Filter:

Messages in week 24 (Jun 05 - Jun 11, 2017)

Threads62 messages
24Started
10Replied in own
28Replied to othersin 16 threads
Patchesof which 3 carried a patch
1New patchfirst in its thread
2Follow-uprevision of an earlier one
ActivityThreadSent
Replied (own)pgsql: Use standard interrupt handling in logical replication launcher.over 9 years ago
Replied (other)logical replication busy-waiting on a lockover 9 years ago
Replied (own)walsender & parallelismover 9 years ago
Replied (other)Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddityover 9 years ago
Replied (other)logical replication busy-waiting on a lockover 9 years ago
Replied (other)Get stuck when dropping a subscription during synchronizing tableover 9 years ago
Started threadpgsql: Use standard interrupt handling in logical replication launcher.over 9 years ago
Replied (own)walsender termination error messages worse in v10over 9 years ago
Started threadpgsql: Again report a useful error message when walreceiver's connectioover 9 years ago
Replied (other)Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddityover 9 years ago
Replied (other)Use of snapshot in logical replicationover 9 years ago
Replied (other)Directory pg_replslot is not properly cleanedover 9 years ago
Replied (other)Fix a typo in snapmgr.cover 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 10b1over 9 years ago
Replied (other)Parallel Aggregation support for aggregate functions that use transitions not implemented for array_aggover 9 years ago
Replied (other)Parallel Aggregation support for aggregate functions that use transitions not implemented for array_aggover 9 years ago
Replied (other)Get stuck when dropping a subscription during synchronizing tableover 9 years ago
Started threadpgsql: 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 patchError while creating subscription when server is running in single user modeover 9 years ago
Replied (own)libpqrcv_PQexec() seems to violate latch protocolover 9 years ago
Replied (own)libpqrcv_PQexec() seems to violate latch protocolover 9 years ago
Started threadlibpqrcv_PQexec() seems to violate latch protocolover 9 years ago
Replied (other)Error while creating subscription when server is running in single user modeover 9 years ago
Replied (other)Parallel Aggregation support for aggregate functions that use transitions not implemented for array_aggover 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 threadpgsql: Remove leftover variable from previous commit.over 9 years ago
Replied (other)Use of non-restart-safe storage by temp_tablespacesover 9 years ago
Replied (other)logical replication and PANIC during shutdown checkpoint in publisherover 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Have walsenders participate in procsignal infrastructure.over 9 years ago
Started threadpgsql: Prevent possibility of panics during shutdown checkpoint.over 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Prevent possibility of panics during shutdown checkpoint.over 9 years ago
Started threadpgsql: Have walsenders participate in procsignal infrastructure.over 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Prevent possibility of panics during shutdown checkpoint.over 9 years ago
Started threadpgsql: Have walsenders participate in procsignal infrastructure.over 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Have walsenders participate in procsignal infrastructure.over 9 years ago
Started threadpgsql: Prevent possibility of panics during shutdown checkpoint.over 9 years ago
Started threadpgsql: Wire up query cancel interrupt for walsender backends.over 9 years ago
Started threadpgsql: Unify SIGHUP handling between normal and walsender backends.over 9 years ago
Started threadpgsql: Revert "Prevent panic during shutdown checkpoint"over 9 years ago
Replied (other)logical replication and PANIC during shutdown checkpoint in publisherover 9 years ago
Replied (other)BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statisticsover 9 years ago
Started threadpgsql: Fix record length computation in pg_waldump/xlogdump.over 9 years ago
Started threadpgsql: Fix record length computation in pg_waldump/xlogdump.over 9 years ago
Started threadpgsql: Fix record length computation in pg_waldump/xlogdump.over 9 years ago
Replied (other)shm_toc_lookup APIover 9 years ago
Replied (other)shm_toc_lookup APIover 9 years ago
Replied (other)Useless assignmentsover 9 years ago
Replied (other)BUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statisticsover 9 years ago
Replied (other)simplehash.h typoover 9 years ago
Replied (other)First patchBUG #14687: pg_xlogdump does only count "main data" for record length and leading to incorrect statisticsover 9 years ago
Replied (other)logical replication and PANIC during shutdown checkpoint in publisherover 9 years ago
Replied (other)Follow-up patchlogical replication and PANIC during shutdown checkpoint in publisherover 9 years ago