| Replied (other) | Collations and Replication; Next Steps | almost 12 years ago |
| Replied (other) | Yet another abort-early plan disaster on 9.3 | almost 12 years ago |
| Replied (other)Follow-up patch | jsonb format is pessimal for toast compression | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: have pg_upgrade fail for old 9.4 JSONB format | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: have pg_upgrade fail for old 9.4 JSONB format | almost 12 years ago |
| Replied (other) | pg_dump -Fd fails to detect ENOSPC | almost 12 years ago |
| Replied (other) | Collation-aware comparisons in GIN opclasses | almost 12 years ago |
| Replied (other) | Collation-aware comparisons in GIN opclasses | almost 12 years ago |
| Replied (other) | KNN-GiST with recheck | almost 12 years ago |
| Replied (other) | KNN-GiST with recheck | almost 12 years ago |
| Replied (other) | jsonb format is pessimal for toast compression | almost 12 years ago |
| Replied (other) | jsonb format is pessimal for toast compression | almost 12 years ago |
| Replied (other) | jsonb format is pessimal for toast compression | almost 12 years ago |
| Replied (other) | proposal: rounding up time value less than its unit. | almost 12 years ago |
| Replied (other) | Yet another abort-early plan disaster on 9.3 | almost 12 years ago |
| Replied (other) | Collations and Replication; Next Steps | almost 12 years ago |
| Replied (other) | Collations and Replication; Next Steps | almost 12 years ago |
| Replied (other) | After upgrade from 9.2.9 to 9.3.5 got reduced contention | almost 12 years ago |
| Replied (own) | formatting.c | almost 12 years ago |
| Started thread | formatting.c | almost 12 years ago |
| Started thread | pgsql: Revert f68dc5d86b9f287f80f4417f5a24d876eb13771d | almost 12 years ago |
| Started thread | pgsql: More formatting.c variable renaming, for clarity | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: adjust C comments | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: preserve the timestamp epoch | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: preserve the timestamp epoch | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (other) | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Replied (other) | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Started thread | pgsql: improve hash creation warning message | almost 12 years ago |
| Replied (other) | Compression of full-page-writes | almost 12 years ago |
| Started thread | pgsql: doc: improve configuration management section | almost 12 years ago |
| Started thread | pgsql: doc: improve configuration management section | almost 12 years ago |
| Replied (other) | [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: compare control version, not catalog version | almost 12 years ago |
| Replied (other) | Inaccuracy in VACUUM's tuple count estimates | almost 12 years ago |
| Replied (other) | "cancelling statement due to user request error" occurs but the transaction has committed. | almost 12 years ago |
| Replied (other)Follow-up patch | pg_control is missing a field for LOBLKSIZE | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: check for large object size compatibility | almost 12 years ago |
| Replied (other) | pg_basebackup failed to back up large file | almost 12 years ago |
| Replied (other) | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Replied (other) | Need Multixact Freezing Docs | almost 12 years ago |
| Started thread | pgsql: Implement mxid_age() to compute multi-xid age | almost 12 years ago |
| Started thread | pgsql: Issue a warning during the creation of hash indexes | almost 12 years ago |
| Replied (other) | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Replied (other) | Memory Alignment in Postgres | almost 12 years ago |
| Replied (other)Follow-up patch | [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (other)Follow-up patch | [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (other) | Memory Alignment in Postgres | almost 12 years ago |
| Replied (other) | Spinlocks and compiler/memory barriers | almost 12 years ago |
| Replied (other) | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Replied (other) | pg_isready --username seems an empty promise | almost 12 years ago |
| Started thread | pgsql: docs: Improve pg_isready details about username/dbname | almost 12 years ago |
| Started thread | pgsql: docs: Improve pg_isready details about username/dbname | almost 12 years ago |
| Replied (other) | btree_gist macaddr valgrind woes | almost 12 years ago |
| Replied (other) | BUG #10330: pg_ctl does not correctly honor "DETACHED_PROCESS" | almost 12 years ago |
| Started thread | pgsql: Properly document that -r is only honored from the command-line. | almost 12 years ago |
| Started thread | pgsql: Properly document that -r is only honored from the command-line. | almost 12 years ago |
| Replied (other)First patch | BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes | almost 12 years ago |
| Replied (other) | pg_dump warnings in MinGW build | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (other)First patch | Need Multixact Freezing Docs | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Replied (own) | Display of timestamp in pg_dump custom format | almost 12 years ago |
| Started thread | pgsql: Report timezone offset in pg_dump/pg_dumpall | almost 12 years ago |
| Replied (other) | pg_upgrade and epoch | almost 12 years ago |
| Started thread | pgsql: pg_upgrade: preserve the timestamp epoch | almost 12 years ago |
| Replied (other) | BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns | almost 12 years ago |
| Replied (other) | BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY | almost 12 years ago |
| Started thread | pgsql: Clarify documentation about "peer" rows in window functions | almost 12 years ago |
| Started thread | pgsql: Clarify documentation about "peer" rows in window functions | almost 12 years ago |
| Replied (other) | [PATCH] parser: optionally warn about missing AS for column and table aliases | almost 12 years ago |
| Started thread | pgsql: Rename C variables in formatting.c, for clarity | almost 12 years ago |
| Replied (own) | Pg_upgrade and toast tables bug discovered | almost 12 years ago |
| Replied (own) | Pg_upgrade and toast tables bug discovered | almost 12 years ago |
| Replied (own) | Pg_upgrade and toast tables bug discovered | almost 12 years ago |
| Replied (own) | Pg_upgrade and toast tables bug discovered | almost 12 years ago |
| Replied (own)Follow-up patch | Display of timestamp in pg_dump custom format | almost 12 years ago |
| Replied (other) | PQputCopyEnd doesn't adhere to its API contract | almost 12 years ago |
| Replied (other) | Join push-down support for foreign tables | almost 12 years ago |
| Replied (other) | Join push-down support for foreign tables | almost 12 years ago |
| Replied (other) | BUG #11353: Documentation for SET AUTOCOMMIT is wrong | almost 12 years ago |
| Replied (other) | Join push-down support for foreign tables | almost 12 years ago |
| Replied (own) | Display of timestamp in pg_dump custom format | almost 12 years ago |
| Replied (own) | Pg_upgrade and toast tables bug discovered | almost 12 years ago |
| Replied (other) | PQputCopyEnd doesn't adhere to its API contract | almost 12 years ago |
| Replied (other)First patch | BUG #10256: COUNT(*) behaves sort of like RANK() when used over a window containing an ORDER BY | almost 12 years ago |
| Started thread | pgsql: Update URL reference material in /contrib/isn docs | almost 12 years ago |
| Started thread | pgsql: Update URL reference material in /contrib/isn docs | almost 12 years ago |
| Replied (other)First patch | dead ISBN link | almost 12 years ago |
| Replied (own)First patch | Display of timestamp in pg_dump custom format | almost 12 years ago |
| Started thread | pgsql: Document use of partial indexes for partial unique constraints | almost 12 years ago |
| Replied (other)First patch | Add link to partial unique index from Constraints (5.3) | almost 12 years ago |
| Started thread | pgsql: Document use of partial indexes for partial unique constraints | almost 12 years ago |
| Replied (other) | BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns | almost 12 years ago |
| Started thread | pgsql: Issue clearer notice when inherited merged columns are moved | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | psql \watch versus \timing | almost 12 years ago |
| Replied (other)First patch | pg_upgrade and epoch | almost 12 years ago |
| Replied (other) | Need Multixact Freezing Docs | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | PL/pgSQL 2 | almost 12 years ago |
| Replied (other) | On partitioning | almost 12 years ago |
| Replied (other)Follow-up patch | BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns | almost 12 years ago |
| Replied (other)Follow-up patch | BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns | almost 12 years ago |
| Replied (other) | On partitioning | almost 12 years ago |
| Replied (other) | On partitioning | almost 12 years ago |