| Replied (other) | Wrong aggregate result when sorting by a NULL value | almost 8 years ago |
| Replied (other) | Trouble Upgrading Postgres | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. | almost 8 years ago |
| Started thread | pgsql: Fix ExecuteCallStmt to not scribble on the passed-in parse tree. | almost 8 years ago |
| Started thread | pgsql: Fix ExecuteCallStmt to not scribble on the passed-in parse tree. | almost 8 years ago |
| Replied (other) | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Started thread | pgsql: Fix bugs in plpgsql's handling of CALL argument lists. | almost 8 years ago |
| Started thread | pgsql: Fix bugs in plpgsql's handling of CALL argument lists. | almost 8 years ago |
| Replied (other) | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Started thread | pgsql: Fix unused-variable warning. | almost 8 years ago |
| Started thread | pgsql: Fix unused-variable warning. | almost 8 years ago |
| Replied (other) | Wrong aggregate result when sorting by a NULL value | almost 8 years ago |
| Replied (other)Follow-up patch | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Replied (other) | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Replied (other) | Wrong aggregate result when sorting by a NULL value | almost 8 years ago |
| Replied (other) | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Replied (other) | bugfix: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" | almost 8 years ago |
| Replied (other) | backend crash on DELETE, reproducible locally | almost 8 years ago |
| Replied (other) | plruby: rb_iterate symbol clash with libruby.so | almost 8 years ago |
| Replied (other) | partitioned indexes and tablespaces | almost 8 years ago |
| Replied (other) | plruby: rb_iterate symbol clash with libruby.so | almost 8 years ago |
| Replied (other) | plruby: rb_iterate symbol clash with libruby.so | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Started thread | pgsql: Make ts_locale.c's character-type functions cope with UTF-16. | almost 8 years ago |
| Replied (other) | BUG #15476: Problem on show_trgm with 4 byte UTF-8 characters | almost 8 years ago |
| Replied (other) | backend crash on DELETE, reproducible locally | almost 8 years ago |
| Replied (other) | BUG #15476: Problem on show_trgm with 4 byte UTF-8 characters | almost 8 years ago |
| Replied (other) | backend crash on DELETE, reproducible locally | almost 8 years ago |
| Replied (other) | pgbench -M option can be specified more than once | almost 8 years ago |
| Replied (other) | pgbench -M option can be specified more than once | almost 8 years ago |
| Started thread | First-draft release notes for back-branch releases | almost 8 years ago |
| Started thread | pgsql: First-draft release notes for 11.1. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Started thread | pgsql: Yet further rethinking of build changes for macOS Mojave. | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | WIP Patch: Add a function that returns binary JSONB as a bytea | almost 8 years ago |
| Replied (other) | Wrong aggregate result when sorting by a NULL value | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | Wrong aggregate result when sorting by a NULL value | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | Vacuum Full does not release the disk size space after delete from table | almost 8 years ago |
| Replied (other) | pgsql: doc: use simpler language for NULL return from ANY/ALL | almost 8 years ago |
| Replied (other) | WIP: Avoid creation of the free space map for small tables | almost 8 years ago |
| Replied (other) | WIP Patch: Add a function that returns binary JSONB as a bytea | almost 8 years ago |
| Replied (other) | Compressed TOAST Slicing | almost 8 years ago |
| Replied (own)Follow-up patch | PG vs macOS Mojave | almost 8 years ago |
| Replied (own)Follow-up patch | PG vs macOS Mojave | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | CF app feature request | almost 8 years ago |
| Replied (own)Follow-up patch | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | backend crash on DELETE, reproducible locally | almost 8 years ago |
| Replied (other) | [PATCH][PROPOSAL] Add enum releation option type | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | backend crash on DELETE, reproducible locally | almost 8 years ago |
| Replied (other) | BUG #15480: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (own) | PG vs macOS Mojave | almost 8 years ago |
| Replied (other) | Should pg 11 use a lot more memory building an spgist index? | almost 8 years ago |
| Replied (other) | Parallel threads in query | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Started thread | pgsql: Fix memory leak in repeated SPGIST index scans. | almost 8 years ago |
| Replied (other) | Super PathKeys (Allowing sort order through precision loss functions) | almost 8 years ago |
| Replied (other) | WIP Patch: Add a function that returns binary JSONB as a bytea | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Sync our copy of the timezone library with IANA release tzcode20 | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Started thread | pgsql: Update time zone data files to tzdata release 2018g. | almost 8 years ago |
| Replied (other) | WIP Patch: Add a function that returns binary JSONB as a bytea | almost 8 years ago |
| Replied (other) | ALTER SERVER SYNTAX ISSUE | almost 8 years ago |
| Replied (own) | Lambda expressions (was Re: BUG #15471) | almost 8 years ago |
| Replied (other) | BEFORE triggers that return NULL can circumvent referential integrity | almost 8 years ago |
| Replied (own) | Lambda expressions (was Re: BUG #15471) | almost 8 years ago |
| Replied (other) | Super PathKeys (Allowing sort order through precision loss functions) | almost 8 years ago |
| Started thread | pgsql: Fix interaction of CASE and ArrayCoerceExpr. | almost 8 years ago |
| Started thread | pgsql: Fix interaction of CASE and ArrayCoerceExpr. | almost 8 years ago |
| Started thread | Lambda expressions (was Re: BUG #15471) | almost 8 years ago |
| Replied (other) | pg_stat_all_tables.last_vacuum not always correct. | almost 8 years ago |
| Replied (other) | Getting fancy errors when accessing information_schema on 10.5 | almost 8 years ago |
| Replied (other) | Getting fancy errors when accessing information_schema on 10.5 | almost 8 years ago |
| Replied (other) | Getting fancy errors when accessing information_schema on 10.5 | almost 8 years ago |
| Replied (other) | BUG #15471: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range | almost 8 years ago |
| Replied (other) | Getting fancy errors when accessing information_schema on 10.5 | almost 8 years ago |
| Replied (other) | Getting fancy errors when accessing information_schema on 10.5 | almost 8 years ago |
| Replied (other) | BUG #15471: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range | almost 8 years ago |
| Replied (other) | Log file | almost 8 years ago |
| Replied (other)First patch | Should pg 11 use a lot more memory building an spgist index? | almost 8 years ago |
| Replied (other) | Log file | almost 8 years ago |
| Replied (other) | date_trunc() in a specific time zone | almost 8 years ago |
| Replied (other) | BUG #15460: Error while creating index or constraint | almost 8 years ago |
| Replied (other) | date_trunc() in a specific time zone | almost 8 years ago |
| Replied (other) | BUG #15460: Error while creating index or constraint | almost 8 years ago |
| Replied (other) | BUG #15460: Error while creating index or constraint | almost 8 years ago |
| Replied (other) | date_trunc() in a specific time zone | almost 8 years ago |
| Replied (other) | BUG #15460: Error while creating index or constraint | almost 8 years ago |
| Replied (other) | BUG #15460: Error while creating index or constraint | almost 8 years ago |
| Replied (other) | pg_promote not marked as parallel-restricted in pg_proc.dat | almost 8 years ago |