| Replied (other) | Info regarding bug list for all previous releases | almost 14 years ago |
| Replied (other) | BUG #6785: Memory Leak in plpgsql | almost 14 years ago |
| Started thread | pgsql: Now that the diskchecker.pl author has updated the download link | almost 14 years ago |
| Started thread | pgsql: Now that the diskchecker.pl author has updated the download link | almost 14 years ago |
| Started thread | pgsql: Now that the diskchecker.pl author has updated the download link | almost 14 years ago |
| Started thread | pgsql: Now that the diskchecker.pl author has updated the download link | almost 14 years ago |
| Replied (other) | Replication/cloning: rsync vs modification dates? | almost 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | almost 14 years ago |
| Replied (other) | Where is diskchecker.pl ? | about 14 years ago |
| Replied (other)First patch | Where is diskchecker.pl ? | about 14 years ago |
| Started thread | pgsql: Update doc mention of diskchecker.pl to add URL for script; reta | about 14 years ago |
| Started thread | pgsql: Update doc mention of diskchecker.pl to add URL for script; reta | about 14 years ago |
| Started thread | pgsql: Update doc mention of diskchecker.pl to add URL for script; reta | about 14 years ago |
| Started thread | pgsql: Update doc mention of diskchecker.pl to add URL for script; reta | about 14 years ago |
| Replied (other) | Replication/cloning: rsync vs modification dates? | about 14 years ago |
| Replied (other) | Where is diskchecker.pl ? | about 14 years ago |
| Replied (other) | Where is diskchecker.pl ? | about 14 years ago |
| Replied (other) | Replication/cloning: rsync vs modification dates? | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Started thread | pgsql: Document that the pg_upgrade user of rsync might want to skip so | about 14 years ago |
| Started thread | pgsql: Document that the pg_upgrade user of rsync might want to skip so | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (other) | PostgreSQL limitations question | about 14 years ago |
| Replied (other) | Covering Indexes | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Started thread | pgsql: Simplify pg_upgrade's handling when returning directory listings | about 14 years ago |
| Started thread | pgsql: Simplify pg_upgrade's handling when returning directory listings | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | Synchronous Standalone Master Redoux | about 14 years ago |
| Replied (other)Follow-up patch | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other)First patch | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | DELETE vs TRUNCATE explanation | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Started thread | 9.2 release schedule | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (own) | Use of rsync for data directory copying | about 14 years ago |
| Replied (other) | Support for XLogRecPtr in expand_fmt_string? | about 14 years ago |
| Replied (other) | Synchronous Standalone Master Redoux | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) | about 14 years ago |
| Replied (other) | WIP pgindent replacement | about 14 years ago |
| Started thread | pgsql: Remove 'x =- 1' check for pgindent, not needed, per report from | about 14 years ago |
| Replied (own) | Re: Documentation and explanatory diagrams | about 14 years ago |
| Replied (other) | Synchronous Standalone Master Redoux | about 14 years ago |
| Replied (other) | Synchronous Standalone Master Redoux | about 14 years ago |
| Replied (own) | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Started thread | pgsql: Document that Log-Shipping Standby Servers cannot be upgraded by | about 14 years ago |
| Started thread | pgsql: Document that Log-Shipping Standby Servers cannot be upgraded by | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Replied (own)Follow-up patch | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own)Follow-up patch | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own)Follow-up patch | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (own)Follow-up patch | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Started threadFirst patch | Using pg_upgrade on log-shipping standby servers | about 14 years ago |
| Replied (other) | Allow replacement of bloated primary key indexes without foreign key rebuilds | about 14 years ago |
| Replied (other) | Allow replacement of bloated primary key indexes without foreign key rebuilds | about 14 years ago |
| Replied (own) | Use of rsync for data directory copying | about 14 years ago |
| Started thread | Use of rsync for data directory copying | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Replied (other) | WAL format changes | about 14 years ago |
| Replied (other) | Problem with pg_upgrade | about 14 years ago |
| Replied (other) | Problem with pg_upgrade | about 14 years ago |
| Replied (other) | Problem with pg_upgrade | about 14 years ago |
| Replied (other) | Last gasp | about 14 years ago |
| Replied (other) | Problem with pg_upgrade | about 14 years ago |
| Replied (other)First patch | obsolete copyright notice | about 14 years ago |
| Started thread | pgsql: Run updated copyright.pl on HEAD and 9.2 trees, updating the psq | about 14 years ago |
| Started thread | pgsql: Run updated copyright.pl on HEAD and 9.2 trees, updating the psq | about 14 years ago |
| Started thread | pgsql: Have copyright.pl skip updating something that is just the curre | about 14 years ago |
| Started thread | pgsql: Have copyright.pl skip updating something that is just the curre | about 14 years ago |
| Started thread | pgsql: Modify copyright.pl so all lines are processed, not just the fir | about 14 years ago |
| Started thread | pgsql: Modify copyright.pl so all lines are processed, not just the fir | about 14 years ago |
| Started thread | pgsql: Fix copyright.pl to properly skip the .git directory by adding a | about 14 years ago |
| Started thread | pgsql: Fix copyright.pl to properly skip the .git directory by adding a | about 14 years ago |
| Started thread | pgsql: Fix spacing in copyright.pl after being run with missing regex s | about 14 years ago |
| Started thread | pgsql: Fix spacing in copyright.pl after being run with missing regex s | about 14 years ago |
| Replied (other) | Covering Indexes | about 14 years ago |
| Started thread | pgsql: Update pg_upgrade comments for recent configpath fix. | about 14 years ago |
| Started thread | pgsql: Update pg_upgrade comments for recent configpath fix. | about 14 years ago |
| Replied (other)First patch | Problem with pg_upgrade | about 14 years ago |
| Started thread | pgsql: Fix PGDATAOLD and PGDATANEW to properly set pgconfig location, p | about 14 years ago |
| Started thread | pgsql: Fix PGDATAOLD and PGDATANEW to properly set pgconfig location, p | about 14 years ago |
| Replied (other) | obsolete copyright notice | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Started thread | pgsql: Fix missing regex slash that caused perltidy to get confused on | about 14 years ago |
| Started thread | pgsql: Fix missing regex slash that caused perltidy to get confused on | about 14 years ago |
| Replied (own) | pgsql: Run pgindent on 9.2 source tree in preparation for first 9.3 | about 14 years ago |
| Started thread | pgsql: Run newly-configured perltidy script on Perl files. | about 14 years ago |
| Started thread | pgsql: Run newly-configured perltidy script on Perl files. | about 14 years ago |
| Started thread | pgsql: Have pg_dump in binary-upgrade mode properly drop user-created | about 14 years ago |
| Started thread | pgsql: Have pg_dump in binary-upgrade mode properly drop user-created | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Replied (other) | Meeting schedule | about 14 years ago |
| Started thread | pgsql: Have copyright tool mention that certain files should be updated | about 14 years ago |
| Replied (other)First patch | outdated legal notice in SGML docs? | about 14 years ago |
| Replied (other) | Pruning the TODO list | about 14 years ago |
| Replied (other) | pgsql: Make the pg_upgrade log files contain actual commands | about 14 years ago |
| Started thread | TODO list updated for 9.3 | about 14 years ago |
| Replied (other) | Uh, I change my mind about commit_delay + commit_siblings (sort of) | about 14 years ago |
| Replied (other) | Posix Shared Mem patch | about 14 years ago |
| Replied (other) | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |
| Replied (other)First patch | BUG #6706: pg_upgrade fails when plpgsql dropped/re-created | about 14 years ago |