| Replied (own) | Sanding down some edge cases for PL/pgSQL reserved words | about 1 year ago |
| Replied (other) | pg_restore - cannot to restore blobs in dictionary format from older pg dumps | about 1 year ago |
| Started thread | pgsql: pg_restore: fix incompatibility with old directory-format dumps. | about 1 year ago |
| Started thread | pgsql: pg_restore: fix incompatibility with old directory-format dumps. | about 1 year ago |
| Replied (other) | pg_restore - cannot to restore blobs in dictionary format from older pg dumps | about 1 year ago |
| Replied (own) | Non-reproducible AIO failure | about 1 year ago |
| Replied (other) | tlsv1 alert unknown ca error on cert authentication | about 1 year ago |
| Replied (other) | BUG #18951: Precision loss in inner join while using SUM aggregate function | about 1 year ago |
| Replied (other) | BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL | about 1 year ago |
| Replied (other) | BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 | about 1 year ago |
| Replied (other) | BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 | about 1 year ago |
| Replied (other) | BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 | about 1 year ago |
| Replied (other) | BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 | about 1 year ago |
| Replied (other) | Feature request: Settings to disable comments and multiple statements in a connection | about 1 year ago |
| Replied (other) | BUG #18948: Equivalent MAX() result in view and inline query yields inconsistent row count | about 1 year ago |
| Replied (other) | Function Error Response Is Not Clear | about 1 year ago |
| Replied (own) | Non-reproducible AIO failure | about 1 year ago |
| Replied (other) | Low OIDs (< 16384) when creating databases in single user mode | about 1 year ago |
| Replied (own) | What's our minimum supported Python version? | about 1 year ago |
| Replied (other) | We should lazy-initialize the deadlock checker state memory | about 1 year ago |
| Replied (own) | Non-reproducible AIO failure | about 1 year ago |
| Replied (own) | gcc 15 "array subscript 0" warning at level -O3 | about 1 year ago |
| Replied (other) | Some questions about gin index | about 1 year ago |
| Started thread | pgsql: Doc: improve description of which role runs a trigger. | about 1 year ago |
| Replied (other) | postmaster uses more CPU in 18 beta1 with io_method=io_uring | about 1 year ago |
| Replied (other) | Wrong security context for deferred triggers? | about 1 year ago |
| Replied (other) | pg18: Virtual generated columns are not (yet) safe when superuser selects from them | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Started thread | pgsql: Doc: you must own the target object to use SECURITY LABEL. | about 1 year ago |
| Replied (other) | Add sentence about SECURITY LABEL object ownership | about 1 year ago |
| Replied (other) | Wrong security context for deferred triggers? | about 1 year ago |
| Started thread | pgsql: Change role names used in trigger test. | about 1 year ago |
| Replied (other) | Yet more ROLE changes in v18 beta1??? | about 1 year ago |
| Replied (other) | Feature request: Settings to disable comments and multiple statements in a connection | about 1 year ago |
| Replied (other) | PG 18 release notes draft committed | about 1 year ago |
| Replied (other) | PG 18 release notes draft committed | about 1 year ago |
| Replied (other) | Yet more ROLE changes in v18 beta1??? | about 1 year ago |
| Replied (other) | Combining scalar and row types in RETURNING | about 1 year ago |
| Replied (other) | autoprewarm_dump_now | about 1 year ago |
| Replied (other) | BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL | about 1 year ago |
| Replied (other) | Combining scalar and row types in RETURNING | about 1 year ago |
| Replied (other) | pg_upgrade: warn about roles with md5 passwords | about 1 year ago |
| Replied (other) | C11 / VS 2019 | about 1 year ago |
| Replied (other) | pg18: Virtual generated columns are not (yet) safe when superuser selects from them | about 1 year ago |
| Replied (other) | pg18: Virtual generated columns are not (yet) safe when superuser selects from them | about 1 year ago |
| Replied (other) | tighten generic_option_name, or store more carefully in catalog? | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Started thread | pgsql: Disallow "=" in names of reloptions and foreign-data options. | about 1 year ago |
| Replied (other) | How to subscribe to pgsql-hackers@postgresql.org | about 1 year ago |
| Replied (other)First patch | tighten generic_option_name, or store more carefully in catalog? | about 1 year ago |
| Replied (own)Follow-up patch | Improve hash join's handling of tuples with null join keys | about 1 year ago |
| Replied (other) | function 'IS JSON ARRAY' not identified | about 1 year ago |
| Replied (other) | SQL:2011 application time | about 1 year ago |