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. Bogosity in contrib/xml2/Makefile
  2. Script binaries renaming
  3. advancing snapshot's xmin
  4. Hash Join Optimization
  5. PG East and Washington DC tour
  6. Re: writing a MIN(RECORD) aggregate
  7. partial dump of patch queue to wiki
  8. GiST opclass and varlena
  9. HP-UX 11.11 PostgreSQL 8.3.1 - psql core dumps - Unresolved symbol: tgetent
  10. Images in PostgreSQL
  11. FETCH FIRST
  12. TRUNCATE TABLE with IDENTITY
  13. Re: [pgsql-www] New email list for emergency communications
  14. Re: RFC: array_agg() per SQL:200n
  15. Re: pl/pgsql Plan Invalidation and search_path
  16. Re: count(*) performance improvement ideas
  17. Commit fest status
  18. Re: [pgsql-www] New email list for emergency communications
  19. Proposal: new ereport option "errdetail_log"
  20. Re: [GSoC] (Is it OK to choose items without % mark in theToDoList) && (is it an acceptable idea to build index on Flash Disk)
  21. Project idea for Google Summer of Code
  22. Re: gcc 4.3 breaks ContribCheck in 8.2 and older.
  23. Re: gcc 4.3 breaks ContribCheck in 8.2 and older.
  24. Bug in libpq causes local clients to hang
  25. TODO Item: Consider allowing control of upper/lower case foldingof unquoted, identifiers
  26. Re: Possible future performance improvement: sortupdates/deletes by ctid
  27. Re: Idea for minor tstore optimization
  28. Re: Sort Refinement
  29. Re: Reworking WAL locking
  30. Re: pg_dump additional options for performance
  31. Building PostgreSQL 8.3.1 on OpenVMS 8.3 AXP
  32. Re: Sort Refinement
  33. serial arrays?
  34. Re: Proposal: new large object API
  35. Commit Fest (was Re: Sort Refinement)
  36. Re: [0/4] Proposal of SE-PostgreSQL patches
  37. Re: [PATCHES] [0/4] Proposal of SE-PostgreSQL patches
  38. How large file is really large - pathconf results
  39. postgresql.org dns problems
  40. Request for feature - ECPGget_PGconn
  41. Re: [0/4] Proposal of SE-PostgreSQL patches
  42. Re: [COMMITTERS] pgsql: Some cleanups of enum-guc code, percomments from Tom.
  43. Remove hacks for old bad qsort() implementations?
  44. Rewriting Free Space Map
  45. Hash index build patch has *worse* performance at small table sizes
  46. strange cost for correlated subquery
  47. Small bug in new backend build method
  48. Single table forcing sequential scans on query plans
  49. Re: Commit fest?
  50. Re: Commit fest?
  51. Re: [COMMITTERS] pgsql: Fix vacuum so that autovacuum is reallynot cancelled when doing
  52. Re: Commit fest?
  53. Re: [DOCS] pg_total_relation_size() and CHECKPOINT
  54. File your tax with NETFILE today
  55. Data Recovery feature
  56. PROC_VACUUM_FOR_WRAPAROUND doesn't work expectedly
  57. Proposal: new large object API
  58. aclitem out/in don't "work"
  59. Proposal for db level triggers
  60. Re: Maybe some more low-hanging fruit in thelatestCompletedXid patch.
  61. TIMESTAMP and daylight savings time question
  62. Move the developers wiki?
  63. Ideas input sought for this year's SOC page
  64. Re: Re: TODO-list on wiki (was: TODO update aboutSQLSTATE to PGconn)
  65. Re: Re: TODO-list on wiki (was: TODO update aboutSQLSTATE to PGconn)
  66. Re: TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)
  67. transaction support in pl/slql
  68. count(*) performance improvement ideas
  69. Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATEseverit yto PGconn return status > >
  70. Re: [NOVICE] encoding problems
  71. Build problem with VS2008 Express Edition
  72. Noob Hints on testing and debugging?
  73. bug in numeric_power() function
  74. Re: Autovacuum vs statement_timeout
  75. Re: Sorted writes in checkpoint
  76. Re: Patch for Prevent pg_dump/pg_restore from beingaffected by statement_timeout
  77. Re: [PATCHES] Fix for large file support(nonsegment mode support)
  78. simple plpgsql / sql function question
  79. Re: Autovacuum vs statement_timeout
  80. [ANN] Now v8.3 based SE-PostgreSQL is available
  81. =?Windows-1251?B?7vTu8Ozo7CDw4Ofw5fjl7ejlIO3gIPDg4e7y8w==?=
  82. Re: [ANNOUNCE] == Postgres Weekly News - March 09 2008 ==
  83. Idea about sql command create table like
  84. COPY issue(gsoc project)
  85. Re: [PATCHES] Fix for large file support (nonsegment mode support)
  86. strange pg_ctl's behavior
  87. LISTEN vs. two-phase commit
  88. Detecting large-file support in configure
  89. [Fwd: Re: [PATCHES] 64-bit CommandIds]
  90. Need -fwrapv or -fno-strict-overflow for gcc-4.3
  91. Cleaning up the commit fest to-do list
  92. Lazy constraints / defaults
  93. [PATCH] Add TimeOffset and DateOffset typedefs
  94. timestamp datatype cleanup
  95. timestamp datatype cleanup
  96. Re: patternsel() and histogram_selectivity() and the hard cutoff of 100
  97. Re: [PATCHES] a tsearch2 (8.2.4) dictionary that only filtersout stopwords
  98. Maximum statistics target
  99. Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severity to PGconnreturn status > >
  100. Re: request feature: alter view add column (or something like)
  101. Commitfest status
  102. Commitfest process
  103. Doubt in heap_release_fetch
  104. Terminating a backend
  105. Intended behaviour of SET search_path with SQL functions?
  106. Behaviour of to_tsquery(stopwords only)
  107. Re: Problem with site doc search
  108. Nasty bug in heap_page_prune
  109. Re: [GENERAL] PostgreSQL 8.3 XML parser seems not torecognize the DOCTYPE element in XML files
  110. buildfarm member fennec crashing in plpython test
  111. Re: Patch to update libpqxx's homepage in README
  112. [SQL] Proposed patch - psql wraps at window width
  113. Re: pg_dump additional options for performance
  114. Re: pg_dump additional options for performance
  115. 8.3.0 Core with concurrent vacuum fulls
  116. Replacing the corrupt "global" folder with older one
  117. How to handle error message in PG_CATCH
  118. pt_br translation
  119. Re: pg_dump additional options for performance
  120. libpq type system 0.9a
  121. HOT and autovacuum
  122. RFD: hexstring(n) data type
  123. Google Summer of Code 2008
  124. Query Builder in pgAdmin for GSoC 2008
  125. Patch application emails
  126. Constructing array
  127. Re: newbie: renaming sequences task
  128. Re: newbie: renaming sequences task
  129. newbie: renaming sequences task
  130. Re: Read-ahead and parallelism in redo recovery
  131. request feature: alter view add column (or something like)
  132. Why we panic in pglz_decompress
  133. Read-ahead and parallelism in redo recovery
  134. A couple of PG schedule reminders
  135. "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables
  136. Need Mentors for Google Summer of Code!
  137. Google SoC 2008?
  138. Silly Newbie question
  139. ES7000 Windows 2003 server 64bit processor
  140. Logging conflicted queries on deadlocks
  141. CREATE TABLE, load and freezing
  142. Buildfarm member gypsy_moth seems not to like alignment patch
  143. Snapshot Reuse
  144. UUID data format 4x-4x-4x-4x-4x-4x-4x-4x
  145. new warning message
  146. Re: [PATCHES] 2WRS [WIP]
  147. Idea for minor tstore optimization
  148. ResourceOwners for Snapshots? holdable portals
  149. Re: Proposal: wildcards in pg_service.conf
  150. proposal: plpgsql return execute ...
  151. select avanced
  152. win32 build problem (cvs, msvc 2005 express)
  153. Full text search - altering the default parser
  154. An idea for parallelizing COPY within one backend
  155. Required make version
  156. Two Coverity Scan volunteers needed
  157. Re: [COMMITTERS] pgsql: Don't build the win32 support files in the all target, only in
  158. Idle idea for improving concurrency of LISTEN/NOTIFY
  159. Varlena Type Creation
  160. Bulk loading performance improvements
  161. pgAgent job limit
  162. Producer/Consumer Issues in the COPY across network
  163. Re: pg_dump additional options for performance
  164. Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the
  165. code cleanup of timestamp code
  166. Re: pg_dump additional options for performance
  167. Reference by in \d <table_name> out
  168. Re: [COMMITTERS] pgsql: Link postgres from all object files atonce, to avoid the
  169. libpq.rc make rule
  170. Re: build environment: a different makefile
  171. Tuning 8.3
  172. Re: [PATCHES] Avahi support for Postgresql
  173. Re: [PATCHES] Avahi support for Postgresql
  174. Re: [PATCHES] Avahi support for Postgresql
  175. One more option for pg_dump...
  176. Strange behavior with leap dates and centuries BC
  177. Questions about indexes with text_pattern_ops
  178. dblink doesn't honor interrupts while waiting a result
  179. insert ... delete ... returning ... ?
  180. Behaviour of rows containg not-null domains in plpgsql
  181. Re: pg_dump additional options for performance
  182. idea: simple variadic functions in SQL and PL/pgSQL
  183. Re: RFP: Recursive query in 8.4
  184. Re: [PATCHES] Avahi support for Postgresql
  185. Improved (De)Serialization Support
  186. Re: RFP: Recursive query in 8.4
  187. Proposed changes to DTrace probe implementation
  188. Re: Permanent settings
  189. Linking backend in one piece
  190. Full-text search default vs specified configuration
  191. Re: RFP: Recursive query in 8.4
  192. Memory leaks on SRF rescan
  193. Re: Permanent settings
  194. Re: Permanent settings
  195. OSSP can be used in the windows environment now!
  196. insufficient data left in message
  197. TO_DATE behavior!
  198. about date/time parser
  199. VARATT_EXTERNAL_GET_POINTER is not quite there yet
  200. Batch update of indexes on data loading
  201. Re: Getting available options
  202. Re: CVS repository invalid revision
  203. Why does pg_ctl.c have its own copy of PM_VERSIONSTR?
  204. Which MemoryContext?
  205. Re: CVS repository invalid revision
  206. Re: Timezone view
  207. Re: ANALYZE to be ignored by VACUUM
  208. Re: Timezone view
  209. Re: Including PL/PgSQL by default
  210. generating non-unicode 8-bit text data in SQL_ASCII encoding
  211. More char()/ascii()
  212. failed assertion in toasting code
  213. Re: Permanent settings
  214. Re: Permanent settings
  215. Re: Permanent settings
  216. longest prefix match
  217. Re: Permanent settings
  218. Re: ANALYZE to be ignored by VACUUM
  219. Re: Permanent settings
  220. Re: Permanent settings
  221. distibuted transactions, SQL+XPath+XTree
  222. testing a post directly on server
  223. gateway test II
  224. minimal update trigger
  225. Re: 8.3 / 8.2.6 restore comparison
  226. TODO item:Allow to_date() and to_timestamp() accept localized month names
  227. Why are we waiting?
  228. release checklist
  229. Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59
  230. Page-at-a-time Locking Considerations
  231. Merge condition in postgresql
  232. Reg: Question about concurrency/locking
  233. NULL OR ZERO
  234. Re: RFC: array_agg() per SQL:200n
  235. clone varlena function
  236. Re: Truncate Triggers
  237. Re: Truncate Triggers
  238. Strange behavior on plpgsql trigger function in if comparison
  239. Run positions on Tape
  240. Problem with site doc search
  241. configurability of OOM killer
  242. Re: BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied
  243. Backward reading
  244. FW: bitemporal functionality for PostgreSQL
  245. Re: Limit changes query plan
  246. Limit changes query plan
  247. [mike.aubury@aubit.com: PGconn ?]
  248. ONLINE TRAINING FOR SAP AND NET WEAVER
  249. [Fwd: [COMMITTERS] pgsql: Stamp 8.3 in CVS.]
  250. <IDLE> and waiting