PDA

View Full Version : pgsql Hackers

Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 [29] 30 31 32 33 34
  1. Re: NOLOGGING option, or ?
  2. SELECT FOR UPDATE and UNION ALL
  3. Re: Can we simplify win32 threading code
  4. Google's Summer of Code ...
  5. fdatasync failed, I/O error
  6. Re: Quick-and-dirty compression for WAL backup blocks
  7. Re: Quick-and-dirty compression for WAL backup blocks
  8. Re: Tablespace-level Block Size Definitions
  9. Re: Can we simplify win32 threading code
  10. regarding storage in postgres
  11. ODBC
  12. audit facilities?
  13. NOLOGGING option, or ?
  14. Physical Tlist optimization still possible?
  15. Quick-and-dirty compression for WAL backup blocks
  16. =?windows-1251?B?ze7z8uHz6ugg4S/zIOjnINHYwCDu8iAzMDAgJCDxIOPg8ODt8ujl6SDiIMzu8eri? ==?windows-1251?B?5SAo7e7i++Ug7+7x8vPv6+Xt6P8p?=
  17. Deadlock with tsearch2 index ...
  18. Re: Deadlock with tsearch2 index ...
  19. CREATE DATABASE fails when template1 being accessed ...
  20. ddl triggers
  21. Consumer-grade vs enterprise-grade disk drives
  22. Re: [PATCHES] Adding \x escape processing to COPY, psql, backend
  23. Autoconf update?
  24. Fix for cross compilation
  25. Interval->day proposal
  26. Re: compiling postgres with Visual Age compiler on OpenPower5 / Linux
  27. Small change in LockAcquire API
  28. Simplifying unknown-literal handling
  29. pg_buffercache causes assertion failure
  30. Re: Inefficiency in recent pgtz patch
  31. compiling postgres with Visual Age compiler on OpenPower5 / Linux
  32. Escape handling in COPY, strings, psql
  33. Inefficiency in recent pgtz patch
  34. Bloom Filter indexes?
  35. Re: thw rewriter and default values, again
  36. Re: thw rewriter and default values, again
  37. INOUT/OUT problems with IMMUTABLE
  38. overlaps() does not work as expected?
  39. Re: logging sql from JDBC
  40. Multiple-statement Rules Incompatible With Constraints
  41. Re: Can we simplify win32 threading code
  42. unsafe use of hash_search(... HASH_ENTER ...)
  43. A 2 phase commit weirdness
  44. Rod Taylor
  45. Regression failures: time, timetz, horology
  46. Re: Can we simplify win32 threading code
  47. Re: Can we simplify win32 threading code
  48. foreign keys and RI triggers
  49. Can we simplify win32 threading code
  50. Josh Narins' Subcountry System
  51. adding a function to pg_proc.h
  52. Re: Cost of XLogInsert CRC calculations
  53. Source Code Help Needed
  54. logging sql from JDBC
  55. WAL replay failure after file truncation(?)
  56. soundex and metaphone
  57. postmaster.pid disappeared
  58. IN/OUT parameters
  59. 8.0.x RPM issues
  60. Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. {}
  61. plpgsql trigger - does it auto-acquire a lock?
  62. Deadlocks in 7.4.x ...
  63. Obtaining Firing Statement clause in (pl/perlu) Trigger Function
  64. Speeding up the Postgres lexer
  65. Re: INSTEAD OF trigger on VIEWs
  66. INSTEAD OF trigger on VIEWs
  67. subquery returning array
  68. Re: Views update ?
  69. SO_KEEPALIVE
  70. Re: inet increment w/ int8
  71. Minor issues with bitmap
  72. Re: Allow change of kerberos service name without recompilation
  73. Re: [GENERAL] Image storage questions
  74. Re: Learning curves and such (was Re: pgFoundry)
  75. Re: Notification when freespaces empty
  76. Re: Notification when freespaces empty
  77. Inherited constraints and search paths (was Re: [GENERAL] Preserving data after updates)
  78. C array from SQL array?
  79. 8.02 rpm error
  80. Re: Bitmap scan cost model (was Re: bitmap scans, btree scans, and tid order)
  81. Re: Bitmap scan cost model (was Re: bitmap scans, btree scans, and tid order)
  82. understanding bitmap index benefit
  83. Contributing
  84. Rationalizing SInval/PGPROC data structures and locking
  85. could not dump unrecognized node type: 500
  86. Two-phase commit issues
  87. Re: patches for items from TODO list
  88. Re: patches for items from TODO list
  89. pg_dump and using schema problem
  90. Re: Learning curves and such (was Re: pgFoundry)
  91. Re: Compiling tsearch2 on AIX
  92. Re: Ingres dump files to PostgreSQL
  93. Re: Learning curves and such (was Re: pgFoundry)
  94. Re: Learning curves and such (was Re: pgFoundry)
  95. SO_KEEPALIVE
  96. postgreSQL as deductive DBMS
  97. postgreSQL as deductive DBMS
  98. bitmap scans, btree scans, and tid order
  99. Re: [ADMIN] Permissions not removed when group dropped
  100. Planned change of ExecRestrPos API
  101. [Fwd: Re: SQL99 Hierarchical queries]
  102. alternate regression dbs?
  103. Re: Server instrumentation for 8.1
  104. Re: Do you have any objections on contributing your improvements of the PostgreSQL core back into the product?
  105. PREPARE TRANSACTION and friends, separate node?
  106. Re: Do you have any objections on contributing your improvements of the PostgreSQL core back into the product?
  107. Re: Views, views, views: Summary of Arguments
  108. Re: Views, views, views: Summary of Arguments
  109. Re: Oracle Style packages on postgres
  110. Re: Server instrumentation for 8.1
  111. libpq lo_open errors when first action in connection
  112. PostgreSQL running out of file handles
  113. Best way to scan on-disk bitmaps
  114. Re: "Priority Mechanisms for OLTP and Transactional Web Applications"
  115. Re: Views, views, views: Summary of Arguments
  116. Re: implementing NOTIFY with message parameter
  117. Re: Server instrumentation for 8.1
  118. Re: SQL_ASCII vs. 7-bit ASCII encodings
  119. Re: Server instrumentation for 8.1
  120. Re: Server instrumentation for 8.1
  121. Re: [ADMIN] how do i kill user sessions?
  122. Re: Server instrumentation for 8.1
  123. SQL_ASCII vs. 7-bit ASCII encodings
  124. patches for items from TODO list
  125. New Contrib Build?
  126. Understanding Rule System
  127. Re: Server instrumentation for 8.1
  128. Re: Oracle Style packages on postgres
  129. Re: [PATCHES] plperl and pltcl installcheck targets
  130. 7.3.10 working
  131. Server instrumentation for 8.1
  132. Re: Oracle Style packages on postgres
  133. --enable-thread-safety?
  134. FW: Views, views, views! (long)
  135. Re: Views, views, views: Summary of Arguments
  136. Adding callback support.
  137. Hashagg planning bug (8.0.1)
  138. Re: Case insensitive usernames
  139. Re: Views, views, views! (long)
  140. Re: Oracle Style packages on postgres
  141. Please clarify
  142. Re: Oracle Style packages on postgres
  143. Re: Patch for collation using ICU
  144. Re: Case insensitive usernames
  145. Re: request for sql3 compliance for the update command
  146. Its all re-packaged ...
  147. Table Partitioning, Part 1
  148. Re: Case insensitive usernames
  149. Re: Views, views, views! (long)
  150. Table Partitioning, Part 1
  151. Re: Patch for collation using ICU
  152. Case insensitive usernames
  153. Re: Can we get patents?
  154. Re-packaging releases ...
  155. Oracle Style packages on postgres
  156. Re: Patch for collation using ICU
  157. Re: Patch for collation using ICU
  158. Re: Patch for collation using ICU
  159. Re: Patch for collation using ICU
  160. Re: [PATCHES] Cleaning up unreferenced table files
  161. Re: Patch for collation using ICU
  162. why two WRITE_NODE_FIELD(whereCluase)?
  163. Re: Patch for collation using ICU
  164. Re: Patch for collation using ICU
  165. Will new release require an initdb?
  166. Re: [GENERAL] Invalid unicode in COPY problem
  167. Re: Patch for collation using ICU
  168. Can we get patents?
  169. Re: Patch for collation using ICU
  170. Re: [GENERAL] Invalid unicode in COPY problem
  171. Re: [GENERAL] Invalid unicode in COPY problem
  172. Re: Patch for collation using ICU
  173. Re: Patch for collation using ICU
  174. Re: Patch for collation using ICU
  175. Re: [GENERAL] Invalid unicode in COPY problem
  176. Fix PID file location?
  177. Re: Patch for collation using ICU
  178. Race conditions, race conditions!
  179. Re: Patch for collation using ICU
  180. Re: Patch for collation using ICU
  181. Re: Patch for collation using ICU
  182. Re: Patch for collation using ICU
  183. Re: Patch for collation using ICU
  184. Re: Patch for collation using ICU
  185. Re: Patch for collation using ICU
  186. Re: Patch for collation using ICU
  187. Re: Patch for collation using ICU
  188. Re: Patch for collation using ICU
  189. Re: Patch for collation using ICU
  190. Re: Patch for collation using ICU
  191. Re: Patch for collation using ICU
  192. Re: Patch for collation using ICU
  193. Re: Patch for collation using ICU
  194. Re: Patch for collation using ICU
  195. rendezvous
  196. unix_socket_directory bug or feature?
  197. Releases postponed till Monday
  198. CVS HEAD problem: psql: symbol lookup error: /usr/lib/libreadline.so.4:
  199. Re: Do you have any objections on contributing your improvements of the PostgreSQL core back into the product?
  200. Re: [pgsql-advocacy] Increased company involvement
  201. Re: [pgsql-advocacy] Increased company involvement
  202. State of Kerberos v4 support
  203. Re: [pgsql-advocacy] Increased company involvement
  204. Re: [pgsql-advocacy] Increased company involvement
  205. Re: [pgsql-advocacy] Increased company involvement
  206. FC3 broken with HEAD
  207. test bed
  208. Database properties not being duplicated
  209. Re: [pgsql-advocacy] Increased company involvement
  210. Re: [pgsql-advocacy] Increased company involvement
  211. Re: [pgsql-advocacy] Increased company involvement
  212. pl/pgsql enabled by default
  213. pgFoundry
  214. Proposed 'cleanup' of ftp ...
  215. Packages 7.2.8 thru 8.0.2 built ...
  216. Re: Views, views, views! (long)
  217. Re: Views, views, views! (long)
  218. Re: Views, views, views! (long)
  219. test, please ignore
  220. Re: [pgsql-advocacy] Increased company involvement
  221. Re: [pgsql-advocacy] Increased company involvement
  222. Re: [pgsql-advocacy] Increased company involvement
  223. Re: [ADMIN] A real puzzler: ANY way to recover?
  224. Re: Views, views, views! (long)
  225. Re: Views, views, views! (long)
  226. Re: Views, views, views! (long)
  227. Re: 'infinity' in GiST index
  228. Re: [GENERAL] Interesting article on transactional algorithms includes
  229. Re: "Priority Mechanisms for OLTP and Transactional Web Applications"
  230. plpgsql SET OF functions in field list of select
  231. Re: Views, views, views! (long)
  232. Views, views, views! (long)
  233. 'infinity' in GiST index
  234. Re: performance of bitmap scans in nested loop joins
  235. Re: SQL99 Hierarchical queries
  236. Re: "Priority Mechanisms for OLTP and Transactional Web Applications"
  237. FW: "Priority Mechanisms for OLTP and Transactional Web Applications"
  238. Re: "Priority Mechanisms for OLTP and Transactional Web Applications"
  239. Re: pg_locks needs a facelift
  240. pgsql-hackers@postgresql.org
  241. Re: [OT] Re: [pgsql-advocacy] Increased company involvement
  242. Re: [pgsql-advocacy] Increased company involvement
  243. Re: A proper fix for the conversion-function problem
  244. Re: A proper fix for the conversion-function problem
  245. Re: inclusions WAS: Increased company involvement
  246. Re: Feature freeze date for 8.1
  247. Re: Feature freeze date for 8.1
  248. Re: Feature freeze date for 8.1
  249. Bogus assertion in multixact.c?
  250. Re: Feature freeze date for 8.1