| Replied (other) | ERROR: insufficient columns in the PRIMARY KEY constraint definition | almost 6 years ago |
| Replied (own) | Why does PostgresNode.pm set such a low value of max_wal_senders? | almost 6 years ago |
| Replied (other) | ERROR: insufficient columns in the PRIMARY KEY constraint definition | almost 6 years ago |
| Replied (other) | ERROR: insufficient columns in the PRIMARY KEY constraint definition | almost 6 years ago |
| Replied (other) | ERROR: insufficient columns in the PRIMARY KEY constraint definition | almost 6 years ago |
| Started thread | Why does PostgresNode.pm set such a low value of max_wal_senders? | almost 6 years ago |
| Replied (own) | Dumping/restoring fails on inherited generated column | almost 6 years ago |
| Replied (other) | BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop | almost 6 years ago |
| Replied (other) | Version 13 documentation layout is harder to read than version 12 | almost 6 years ago |
| Replied (other) | Version 13 documentation layout is harder to read than version 12 | almost 6 years ago |
| Replied (other) | Compile 12.2 with specific OpenSSL libraries | almost 6 years ago |
| Replied (other) | Compile 12.2 with specific OpenSSL libraries | almost 6 years ago |
| Replied (other)Follow-up patch | BUG #16419: wrong parsing BC year in to_date() function | almost 6 years ago |
| Replied (other) | BUG #16419: wrong parsing BC year in to_date() function | almost 6 years ago |
| Started thread | pgsql: Fix make_timestamp[tz] to accept negative years as meaning BC. | almost 6 years ago |
| Replied (other) | BUG #16419: wrong parsing BC year in to_date() function | almost 6 years ago |
| Replied (own) | Dumping/restoring fails on inherited generated column | almost 6 years ago |
| Replied (other) | BUG #16622: pg_dump produces erroneus ALTER TABLE statement for a table with an inherited generated column | almost 6 years ago |
| Replied (own) | Dumping/restoring fails on inherited generated column | almost 6 years ago |
| Replied (other) | Planner making bad choice in alternative subplan decision | almost 6 years ago |
| Replied (other) | calling procedures is slow and consumes extra much memory against calling function | almost 6 years ago |
| Started thread | pgsql: Fix memory leak in plpgsql's CALL processing. | almost 6 years ago |
| Started thread | pgsql: Fix memory leak in plpgsql's CALL processing. | almost 6 years ago |
| Started thread | pgsql: Fix memory leak in plpgsql's CALL processing. | almost 6 years ago |
| Started thread | pgsql: Fix memory leak in plpgsql's CALL processing. | almost 6 years ago |
| Replied (other) | Version 13 documentation layout is harder to read than version 12 | almost 6 years ago |
| Replied (other) | Version 13 documentation layout is harder to read than version 12 | almost 6 years ago |
| Replied (other) | pgsql: Change SHA2 implementation based on OpenSSL to use EVP digest ro | almost 6 years ago |
| Replied (other) | Small improvements to pg_list.h's linitial(), lsecond(), lthird() etc macros | almost 6 years ago |
| Started thread | pgsql: Add for_each_from, to simplify loops starting from non-first lis | almost 6 years ago |
| Started thread | pgsql: Add for_each_from, to simplify loops starting from non-first lis | almost 6 years ago |