Filter:

Messages in week 46 (Nov 09 - Nov 15, 2020)

Threads74 messages
28Started
2Replied in own
44Replied to othersin 17 threads
Patchesof which 8 carried a patch
3New patchfirst in its thread
5Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Issue upgrading from 9.5 to 13 with pg_upgrade: "connection to database failed: FATAL: database "template1" does not exist"over 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)public schema default ACLover 5 years ago
Replied (own)First patchpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Replied (other)Follow-up patchAdd important info about ANALYZE after create Functional Indexover 5 years ago
Replied (other)Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.htmlover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Started threadpgsql: doc: clarify where to find pg_type_d.h (PG 11+) and pg_type.hover 5 years ago
Replied (other)Add important info about ANALYZE after create Functional Indexover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Started threadpgsql: docs: mention that expression indexes need analyzeover 5 years ago
Replied (other)Minor documentation error regarding streaming replication protocolover 5 years ago
Replied (other)Proposition for autoname columnsover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: doc: wire protocol data type for history file content is byteaover 5 years ago
Started threadpgsql: change wire protocol data type for history file contentover 5 years ago
Replied (other)Proposition for autoname columnsover 5 years ago
Replied (other)Encryption with customer provided key in a multi tenant Postgres JSONB DBover 5 years ago
Replied (other)Follow-up patchWhat does "[backends] should seldom or never need to wait for a write to occur" mean?over 5 years ago
Replied (other)BUG #16713: Can't load serverover 5 years ago
Replied (other)Proposition for autoname columnsover 5 years ago
Replied (other)Follow-up patchWhat does "[backends] should seldom or never need to wait for a write to occur" mean?over 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Christopher Browneover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Proposition for autoname columnsover 5 years ago
Replied (other)Follow-up patchWhat does "[backends] should seldom or never need to wait for a write to occur" mean?over 5 years ago
Replied (other)BUG #16708: Please add some more restrictions to the default systemd unit filesover 5 years ago
Replied (other)New "function tables" in V13 documentationover 5 years ago
Replied (other)BUG #16708: Please add some more restrictions to the default systemd unit filesover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)BUG #16708: Please add some more restrictions to the default systemd unit filesover 5 years ago
Replied (other)Add docs stub for recovery.confover 5 years ago
Replied (other)Addition to contentover 5 years ago
Replied (other)Prevent printing "next step instructions" in initdb and pg_upgradeover 5 years ago
Replied (other)Prevent printing "next step instructions" in initdb and pg_upgradeover 5 years ago
Replied (other)Prevent printing "next step instructions" in initdb and pg_upgradeover 5 years ago
Replied (other)Proposition for autoname columnsover 5 years ago
Replied (other)Prevent printing "next step instructions" in initdb and pg_upgradeover 5 years ago
Replied (other)First patchMissing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.htmlover 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Replied (other)BUG #16486: Prompted password is ignored when password specified in connection stringover 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Started threadpgsql: doc: fix spelling "connction" to "connection"over 5 years ago
Replied (other)Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.htmlover 5 years ago
Replied (other)cutting down the TODO list threadover 5 years ago
Replied (other)Missing file is mentioned on page https://www.postgresql.org/docs/13/libpq-exec.htmlover 5 years ago
Replied (other)First patchWhat does "[backends] should seldom or never need to wait for a write to occur" mean?over 5 years ago
Replied (other)What does "[backends] should seldom or never need to wait for a write to occur" mean?over 5 years ago
Replied (other)Follow-up patchAdd important info about ANALYZE after create Functional Indexover 5 years ago
Replied (other)public schema default ACLover 5 years ago
Replied (other)public schema default ACLover 5 years ago
Replied (own)Temporary tables versus wraparound... againover 5 years ago