| Replied (other)Follow-up patch | BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events | almost 5 years ago |
| Replied (other) | BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Started thread | pgsql: Make pg_regexec() robust against out-of-range search_start. | almost 5 years ago |
| Replied (other) | new regexp_*(text, text, int) functions crash | almost 5 years ago |
| Replied (other) | Added missing invalidations for all tables publication | almost 5 years ago |
| Replied (other) | BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 | almost 5 years ago |
| Replied (other) | Increase value of OUTER_VAR | almost 5 years ago |
| Replied (other)Follow-up patch | Increase value of OUTER_VAR | almost 5 years ago |
| Replied (other)Follow-up patch | missing warning in pg_import_system_collations | almost 5 years ago |
| Replied (other) | Remove_temp_files_after_crash and significant recovery/startup time | almost 5 years ago |
| Replied (other) | BUG #17158: Distinct ROW fails with Postgres 14 | almost 5 years ago |
| Started thread | pgsql: Fix some anomalies with NO SCROLL cursors. | almost 5 years ago |
| Started thread | pgsql: Fix some anomalies with NO SCROLL cursors. | almost 5 years ago |
| Started thread | pgsql: Fix some anomalies with NO SCROLL cursors. | almost 5 years ago |
| Started thread | pgsql: Fix some anomalies with NO SCROLL cursors. | almost 5 years ago |
| Started thread | pgsql: Fix some anomalies with NO SCROLL cursors. | almost 5 years ago |
| Replied (own)First patch | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (own) | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | missing warning in pg_import_system_collations | almost 5 years ago |
| Replied (own) | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | How to observe plan_cache_mode transition from custom to generic plan? | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | pgsql: Avoid fetching from an already-terminated plan. | almost 5 years ago |
| Started thread | We don't enforce NO SCROLL cursor restrictions | almost 5 years ago |
| Replied (other) | Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor | almost 5 years ago |
| Replied (other) | How to observe plan_cache_mode transition from custom to generic plan? | almost 5 years ago |
| Replied (other) | BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Started thread | pgsql: Check for relation length overrun soon enough. | almost 5 years ago |
| Replied (other) | missing warning in pg_import_system_collations | almost 5 years ago |
| Replied (other) | trap instead of error on 32 TiB table | almost 5 years ago |
| Replied (other) | trap instead of error on 32 TiB table | almost 5 years ago |
| Replied (other) | Regression in PG14 LookupFuncName | almost 5 years ago |
| Replied (other) | [PATCH] support tab-completion for single quote input with equal sign | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Avoid useless malloc/free traffic around getFormattedTypeName(). | almost 5 years ago |
| Started thread | pgsql: Fix misleading comments about TOAST access macros. | almost 5 years ago |
| Started thread | pgsql: Fix misleading comments about TOAST access macros. | almost 5 years ago |
| Replied (other) | VARDATA_COMPRESSED_GET_COMPRESS_METHOD comment? | almost 5 years ago |
| Replied (other) | [PATCH] Add tab-complete for backslash commands | almost 5 years ago |
| Started thread | pgsql: In psql tab completion, offer spelled-out commands not abbreviat | almost 5 years ago |
| Replied (other) | Warn against transaction level advisory locks for emulating "flat file" DBMS locking strategies | almost 5 years ago |
| Replied (other) | Fix erroneous parallel execution when modifying CTE is present in rewritten query | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Started thread | pgsql: Fix rewriter to set hasModifyingCTE correctly on rewritten queri | almost 5 years ago |
| Replied (other) | Bug in query rewriter - hasModifyingCTE not getting set | almost 5 years ago |
| Replied (other) | No xmin in pg_database | almost 5 years ago |
| Replied (other) | BUG #17184: When using openssl, the memory of a static variable is not freed in libpq | almost 5 years ago |
| Replied (other) | Non-decimal integer literals | almost 5 years ago |
| Replied (other) | Allow escape in application_name (was: [postgres_fdw] add local pid to fallback_application_name) | almost 5 years ago |
| Replied (other) | Bug in query rewriter - hasModifyingCTE not getting set | almost 5 years ago |
| Replied (other) | [PATCH] Add tab-complete for backslash commands | almost 5 years ago |
| Replied (other)Follow-up patch | Correct handling of blank/commented lines in PSQL interactive-mode history | almost 5 years ago |
| Replied (other) | Correct handling of blank/commented lines in PSQL interactive-mode history | almost 5 years ago |
| Replied (other) | EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails | almost 5 years ago |
| Replied (other) | [PATCH] Add `verify-system` sslmode to use system CA pool for server cert | almost 5 years ago |
| Replied (other) | [PATCH] Add `verify-system` sslmode to use system CA pool for server cert | almost 5 years ago |
| Replied (other) | [PATCH] Add `verify-system` sslmode to use system CA pool for server cert | almost 5 years ago |
| Started thread | pgsql: Finish reverting 3eda9fc09fd6b9a1aec2d0113c633c69c3214b4d. | almost 5 years ago |
| Replied (other) | Data loss when '"json_populate_recorset" with long column name | almost 5 years ago |
| Replied (other) | [BUG?] SET TIME ZONE doesn't work with abbreviations | almost 5 years ago |
| Replied (other) | How to log bind values for statements that produce errors | almost 5 years ago |
| Started thread | pgsql: Further fix psql query-cancel test. | almost 5 years ago |
| Replied (other) | [PATCH] Add `verify-system` sslmode to use system CA pool for server cert | almost 5 years ago |
| Replied (other) | BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events | almost 5 years ago |
| Replied (other) | Timeout failure in 019_replslot_limit.pl | almost 5 years ago |
| Replied (other) | Behavior change in PostgreSQL 14Beta3 or bug? | almost 5 years ago |
| Replied (other) | Patch: shouldn't timezone(text, timestamp[tz]) be STABLE? | almost 5 years ago |
| Started thread | pgsql: Fix actively-misleading comments about the contents of struct pg | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Fix bogus timetz_zone() results for DYNTZ abbreviations. | almost 5 years ago |
| Started thread | pgsql: Make timetz_zone() stable, and correct a bug for DYNTZ abbreviat | almost 5 years ago |
| Replied (other) | pg_upgrade - fe_sendauth: no password supplied | almost 5 years ago |