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