| Replied (other) | BUG #14718: unable to update table with identity column GENERATED ALWAYS | about 9 years ago |
| Replied (other) | Apparent walsender bug triggered by logical replication | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create(). | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (own) | Fast promotion not used when doing a recovery_target PITR restore? | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (own) | memory layouts for binary search in nbtree | about 9 years ago |
| Replied (own) | Fast promotion not used when doing a recovery_target PITR restore? | about 9 years ago |
| Replied (own) | memory layouts for binary search in nbtree | about 9 years ago |
| Replied (own) | memory layouts for binary search in nbtree | about 9 years ago |
| Replied (other) | Error in SPI_execute_plan (when inserting JSON from C code first { simboll is lost) | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Reducing pg_ctl's reaction time | about 9 years ago |
| Replied (other) | Another reason why the recovery tests take a long time | about 9 years ago |
| Replied (other) | Another reason why the recovery tests take a long time | about 9 years ago |
| Replied (other) | BUG #14714: long running sessions from remote instance seems to hang some times | about 9 years ago |
| Replied (other)Follow-up patch | subscription worker signalling wal writer too much | about 9 years ago |
| Replied (other) | Logical replication: stuck spinlock at ReplicationSlotRelease | about 9 years ago |
| Replied (other) | Fix a typo in snapmgr.c | about 9 years ago |
| Replied (other) | REPLICA IDENTITY FULL | about 9 years ago |
| Replied (other) | BUG #14714: long running sessions from remote instance seems to hang some times | about 9 years ago |
| Replied (other) | Fix a typo in snapmgr.c | about 9 years ago |
| Started thread | Dynamic instrumentation of lwlock wait times (lwlock flamegraphs) | about 9 years ago |
| Replied (other) | possible self-deadlock window after bad ProcessStartupPacket | about 9 years ago |
| Replied (other) | possible self-deadlock window after bad ProcessStartupPacket | about 9 years ago |
| Replied (own) | Fast promotion not used when doing a recovery_target PITR restore? | about 9 years ago |
| Replied (other) | pglogical vs. built-in logical replication in pg-10 | about 9 years ago |
| Replied (other) | pglogical vs. built-in logical replication in pg-10 | about 9 years ago |
| Replied (other) | lseek/read/write overhead becomes visible at scale .. | about 9 years ago |
| Replied (other) | PATCH: Batch/pipelining support for libpq | about 9 years ago |
| Replied (other) | pg_terminate_backend can terminate background workers and autovacuum launchers | about 9 years ago |
| Replied (other) | An attempt to reduce WALWriteLock contention | about 9 years ago |
| Replied (other)Follow-up patch | PATCH: Batch/pipelining support for libpq | about 9 years ago |
| Replied (other) | PATCH: Batch/pipelining support for libpq | about 9 years ago |
| Replied (other) | PATCH: Batch/pipelining support for libpq | about 9 years ago |
| Replied (other) | pgsql: Restart logical replication launcher when killed | about 9 years ago |
| Replied (other) | PATCH: Batch/pipelining support for libpq | about 9 years ago |
| Replied (other) | Re-indent HEAD tomorrow? | about 9 years ago |
| Replied (own) | Phantom segment upon promotion causing troubles. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | pgsql: Fix possibility of creating a "phantom" segment after promotion. | about 9 years ago |
| Started thread | Broken O(n^2) avoidance in wal segment recycling. | about 9 years ago |
| Started thread | Fast promotion not used when doing a recovery_target PITR restore? | about 9 years ago |
| Started thread | archive_timeout ignored directly after promotion | about 9 years ago |
| Replied (other) | pg_bsd_indent 2.0 is available from git.postgresql.org | about 9 years ago |
| Replied (other) | Optional message to user when terminating/cancelling backend | over 9 years ago |
| Replied (other) | REPLICA IDENTITY FULL | over 9 years ago |
| Replied (other) | REPLICA IDENTITY FULL | over 9 years ago |
| Replied (other) | REPLICA IDENTITY FULL | over 9 years ago |
| Replied (other) | REPLICA IDENTITY FULL | over 9 years ago |
| Replied (other) | effective_io_concurrency increasing | over 9 years ago |
| Replied (other) | PATCH: Batch/pipelining support for libpq | over 9 years ago |
| Replied (own) | Phantom segment upon promotion causing troubles. | over 9 years ago |
| Started thread | Phantom segment upon promotion causing troubles. | over 9 years ago |
| Replied (other) | Directory pg_replslot is not properly cleaned | over 9 years ago |
| Started thread | pgsql: Fix leaking of small spilled subtransactions during logical deco | over 9 years ago |
| Replied (other) | Too many files in pg_replslot folder | over 9 years ago |
| Started thread | pgsql: Fix leaking of small spilled subtransactions during logical deco | over 9 years ago |
| Started thread | pgsql: Fix leaking of small spilled subtransactions during logical deco | over 9 years ago |
| Started thread | pgsql: Fix leaking of small spilled subtransactions during logical deco | over 9 years ago |
| Replied (other) | BUG #14699: Statement trigger and logical replication | over 9 years ago |
| Replied (other) | Preliminary results for proposed new pgindent implementation | over 9 years ago |
| Replied (other) | Preliminary results for proposed new pgindent implementation | over 9 years ago |
| Replied (other) | Preliminary results for proposed new pgindent implementation | over 9 years ago |
| Replied (other) | pg_waldump command line arguments | over 9 years ago |
| Replied (other) | Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby | over 9 years ago |
| Replied (other) | Making server name part of the startup message | over 9 years ago |
| Replied (other) | Preliminary results for proposed new pgindent implementation | over 9 years ago |
| Replied (other) | WIP: Data at rest encryption | over 9 years ago |
| Replied (other) | WIP Patch: Pgbench Serialization and deadlock errors | over 9 years ago |
| Replied (other) | v10beta pg_catalog diagrams | over 9 years ago |
| Replied (other) | v10beta pg_catalog diagrams | over 9 years ago |
| Replied (other) | subscription worker signalling wal writer too much | over 9 years ago |
| Replied (other) | subscription worker signalling wal writer too much | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Started thread | pgsql: Don't force-assign transaction id when exporting a snapshot. | over 9 years ago |
| Replied (other) | Disallowing multiple queries per PQexec() | over 9 years ago |
| Replied (other) | v10beta pg_catalog diagrams | over 9 years ago |
| Replied (other) | v10beta pg_catalog diagrams | over 9 years ago |
| Replied (other) | pgsql: Assert that we don't invent relfilenodes or type OIDs in binary | over 9 years ago |
| Replied (own) | Why are we restricting exported snapshots in subtransactions? | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Started thread | Why are we restricting exported snapshots in subtransactions? | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (own) | Relpartbound, toasting and pg_class | over 9 years ago |
| Replied (own) | Relpartbound, toasting and pg_class | over 9 years ago |
| Replied (other) | Transactional sequence stuff breaks pg_upgrade | over 9 years ago |
| Replied (other) | Transactional sequence stuff breaks pg_upgrade | over 9 years ago |
| Replied (own) | Relpartbound, toasting and pg_class | over 9 years ago |
| Replied (other) | Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby | over 9 years ago |
| Replied (other) | Transactional sequence stuff breaks pg_upgrade | over 9 years ago |
| Replied (other) | Transactional sequence stuff breaks pg_upgrade | over 9 years ago |
| Started thread | Relpartbound, toasting and pg_class | over 9 years ago |
| Replied (other) | standby server crashes hard on out-of-disk-space in HEAD | over 9 years ago |
| Replied (own) | pgsql: Use standard interrupt handling in logical replication launcher. | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Replied (own) | walsender & parallelism | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Replied (other) | Get stuck when dropping a subscription during synchronizing table | over 9 years ago |
| Started thread | pgsql: Use standard interrupt handling in logical replication launcher. | over 9 years ago |
| Replied (own) | walsender termination error messages worse in v10 | over 9 years ago |
| Started thread | pgsql: Again report a useful error message when walreceiver's connectio | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | Use of snapshot in logical replication | over 9 years ago |
| Replied (other) | Directory pg_replslot is not properly cleaned | over 9 years ago |
| Replied (other) | Fix a typo in snapmgr.c | over 9 years ago |
| Replied (other) | Challenges preventing us moving to 64 bit transaction id (XID)? | over 9 years ago |
| Replied (other) | Notes on testing Postgres 10b1 | over 9 years ago |
| Replied (other) | Parallel Aggregation support for aggregate functions that use transitions not implemented for array_agg | over 9 years ago |
| Replied (other) | Parallel Aggregation support for aggregate functions that use transitions not implemented for array_agg | over 9 years ago |
| Replied (other) | Get stuck when dropping a subscription during synchronizing table | over 9 years ago |
| Started thread | pgsql: Clean up latch related code. | over 9 years ago |
| Replied (own) | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Replied (own) | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Replied (other)Follow-up patch | Error while creating subscription when server is running in single user mode | over 9 years ago |
| Replied (own) | libpqrcv_PQexec() seems to violate latch protocol | over 9 years ago |
| Replied (own) | libpqrcv_PQexec() seems to violate latch protocol | over 9 years ago |
| Started thread | libpqrcv_PQexec() seems to violate latch protocol | over 9 years ago |
| Replied (other) | Error while creating subscription when server is running in single user mode | over 9 years ago |
| Replied (other) | Parallel Aggregation support for aggregate functions that use transitions not implemented for array_agg | over 9 years ago |
| Replied (own) | Should we standardize on a type for signal handler flags? | over 9 years ago |
| Replied (own) | Should we standardize on a type for signal handler flags? | over 9 years ago |
| Replied (own) | Should we standardize on a type for signal handler flags? | over 9 years ago |
| Started thread | pgsql: Remove leftover variable from previous commit. | over 9 years ago |
| Replied (other) | Use of non-restart-safe storage by temp_tablespaces | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Have walsenders participate in procsignal infrastructure. | over 9 years ago |
| Started thread | pgsql: Prevent possibility of panics during shutdown checkpoint. | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Have walsenders participate in procsignal infrastructure. | over 9 years ago |
| Started thread | pgsql: Prevent possibility of panics during shutdown checkpoint. | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Prevent possibility of panics during shutdown checkpoint. | over 9 years ago |
| Started thread | pgsql: Have walsenders participate in procsignal infrastructure. | over 9 years ago |
| Started thread | pgsql: Unify SIGHUP handling between normal and walsender backends. | over 9 years ago |
| Started thread | pgsql: Revert "Prevent panic during shutdown checkpoint" | over 9 years ago |
| Started thread | pgsql: Have walsenders participate in procsignal infrastructure. | over 9 years ago |
| Started thread | pgsql: Wire up query cancel interrupt for walsender backends. | over 9 years ago |
| Started thread | pgsql: Prevent possibility of panics during shutdown checkpoint. | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (other) | BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statistics | over 9 years ago |
| Started thread | pgsql: Fix record length computation in pg_waldump/xlogdump. | over 9 years ago |
| Started thread | pgsql: Fix record length computation in pg_waldump/xlogdump. | over 9 years ago |
| Started thread | pgsql: Fix record length computation in pg_waldump/xlogdump. | over 9 years ago |
| Replied (other) | shm_toc_lookup API | over 9 years ago |
| Replied (other) | shm_toc_lookup API | over 9 years ago |
| Replied (other) | Useless assignments | over 9 years ago |
| Replied (other) | BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statistics | over 9 years ago |
| Replied (other) | simplehash.h typo | over 9 years ago |
| Replied (other)First patch | BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statistics | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (other)Follow-up patch | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (own) | Should we standardize on a type for signal handler flags? | over 9 years ago |
| Replied (other) | BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statistics | over 9 years ago |
| Started thread | Should we standardize on a type for signal handler flags? | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | pg_upgrade and missing loadable libraries | over 9 years ago |
| Replied (other) | Index created in BEFORE trigger not updated during INSERT | over 9 years ago |
| Replied (own) | COPY (query) TO ... doesn't allow parallelism | over 9 years ago |
| Replied (own) | walsender & parallelism | over 9 years ago |
| Replied (own) | walsender & parallelism | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Replied (other) | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity | over 9 years ago |
| Started thread | pgsql: Allow parallelism in COPY (query) TO ...; | over 9 years ago |
| Started thread | pgsql: Allow parallelism in COPY (query) TO ...; | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Replied (other)Follow-up patch | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (own) | walsender termination error messages worse in v10 | over 9 years ago |
| Replied (other) | Error while creating subscription when server is running in single user mode | over 9 years ago |
| Started thread | walsender termination error messages worse in v10 | over 9 years ago |
| Replied (other) | Do we need the gcc feature "__builtin_expect" to promote the branches prediction? | over 9 years ago |
| Replied (own) | walsender & parallelism | over 9 years ago |
| Replied (other) | Error while creating subscription when server is running in single user mode | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (other) | logical replication and PANIC during shutdown checkpoint in publisher | over 9 years ago |
| Replied (other) | Concurrent ALTER SEQUENCE RESTART Regression | over 9 years ago |
| Started thread | pgsql: Modify sequence catalog tuple before invoking post alter hook. | over 9 years ago |
| Started thread | pgsql: Make ALTER SEQUENCE, including RESTART, fully transactional. | over 9 years ago |
| Replied (own) | COPY (query) TO ... doesn't allow parallelism | over 9 years ago |
| Replied (other) | logical replication busy-waiting on a lock | over 9 years ago |
| Replied (other) | Hash Functions | over 9 years ago |
| Replied (other) | Effect of changing the value for PARALLEL_TUPLE_QUEUE_SIZE | over 9 years ago |
| Replied (own) | COPY (query) TO ... doesn't allow parallelism | over 9 years ago |
| Replied (own) | COPY (query) TO ... doesn't allow parallelism | over 9 years ago |
| Replied (own) | walsender & parallelism | over 9 years ago |
| Replied (other) | Replication origins and timelines | over 9 years ago |
| Replied (other) | Replication origins and timelines | over 9 years ago |
| Replied (other) | Replication origins and timelines | over 9 years ago |
| Started thread | tap tests on older branches fail if concurrency is used | over 9 years ago |
| Replied (other)Follow-up patch | Concurrent ALTER SEQUENCE RESTART Regression | over 9 years ago |