time server - Search results in mailing lists
Mailing lists >> pgsql-committers >> Thread
2025-04-22 22:10:55 | pgsql: Re-enable SSL connect_fails tests, and fix related race conditio (Tom Lane)
server's log_min_messages setting to DEBUG2 so that the postmaster will log child-process exit, and then wait till we see that log entry before checking for the messages we are actually interested
Mailing lists >> pgsql-committers >> Thread
2025-04-08 01:59:18 | pgsql: Flush the IO statistics of active WAL senders more frequently (Michael Paquier)
timing calculated based on the existing GetCurrentTimestamp() done before the sleeps done to wait for some activity. Note that the sleep done for logical and physical WAL senders happens in two different code paths
Mailing lists >> pgsql-committers >> Thread
2025-04-08 01:59:18 | pgsql: Flush the IO statistics of active WAL senders more frequently (Michael Paquier)
timing calculated based on the existing GetCurrentTimestamp() done before the sleeps done to wait for some activity. Note that the sleep done for logical and physical WAL senders happens in two different code paths
Mailing lists >> pgsql-committers >> Thread
2025-04-08 01:59:18 | pgsql: Flush the IO statistics of active WAL senders more frequently (Michael Paquier)
timing calculated based on the existing GetCurrentTimestamp() done before the sleeps done to wait for some activity. Note that the sleep done for logical and physical WAL senders happens in two different code paths
Mailing lists >> pgsql-committers >> Thread
2025-04-02 16:43:17 | pgsql: libpq: Add min/max_protocol_version connection options (Heikki Linnakangas)
server. Currently only 3.0 is supported, but that will change in a future commit that bumps the protocol version. Even after that version bump the default will likely stay 3.0 for the time
Mailing lists >> pgsql-committers >> Thread
2025-03-19 06:46:08 | pgsql: oauth: Use IPv4-only issuer in oauth_validator tests (Thomas Munro)
server.py does not listen on IPv6. Most of the time, libcurl happily falls back
Mailing lists >> pgsql-committers >> Thread
2025-03-19 05:42:41 | pgsql: Introduce io_max_combine_limit. (Thomas Munro)
server startup time, and functions as a silent clamp on the user setting. That in itself
Mailing lists >> pgsql-committers >> Thread
2025-02-19 07:14:17 | pgsql: Invalidate inactive replication slots. (Amit Kapila)
time of checkpoint. Because checkpoints happen checkpoint_timeout intervals, there can be some lag between when the idle_replication_slot_timeout was exceeded and when the slot invalidation is triggered at the next checkpoint
Mailing lists >> pgsql-committers >> Thread
2025-01-07 00:02:10 | pgsql: Allow changing autovacuum_max_workers without restarting. (Nathan Bossart)
server will only start up to autovacuum_worker_slots workers at a given time. If autovacuum
Mailing lists >> pgsql-committers >> Thread
2024-12-20 03:11:45 | pgsql: Replace durable_rename_excl() by durable_rename(), take two (Michael Paquier)
server, but as mentioned above, it will still overwrite files on some platforms. Second, xlog.c uses it to recycle past WAL segments, where an overwrite should not happen (origin of the change at f0e37a8) because
Mailing lists >> pgsql-committers >> Thread
2024-12-20 03:11:45 | pgsql: Replace durable_rename_excl() by durable_rename(), take two (Michael Paquier)
server, but as mentioned above, it will still overwrite files on some platforms. Second, xlog.c uses it to recycle past WAL segments, where an overwrite should not happen (origin of the change at f0e37a8) because
Mailing lists >> pgsql-committers >> Thread
2024-12-20 03:11:45 | pgsql: Replace durable_rename_excl() by durable_rename(), take two (Michael Paquier)
server, but as mentioned above, it will still overwrite files on some platforms. Second, xlog.c uses it to recycle past WAL segments, where an overwrite should not happen (origin of the change at f0e37a8) because
Mailing lists >> pgsql-committers >> Thread
2024-11-14 17:13:15 | pgsql: Kill dead-end children when there's nothing else left (Heikki Linnakangas)
server from shutting down, it seems better to kill it immediately. It's particularly important, if there was a bug in the early startup code that prevented a dead-end child from timing
Mailing lists >> pgsql-committers >> Thread
2024-10-22 17:26:01 | pgsql: Restructure foreign key handling code for ATTACH/DETACH (Álvaro Herrera)
server failing to throw the required errors. !!! Note that this means existing databases with FKs that reference partitioned tables might have rows that break relational integrity, on tables that were once partitions on the referencing
Mailing lists >> pgsql-committers >> Thread
2024-10-22 17:26:01 | pgsql: Restructure foreign key handling code for ATTACH/DETACH (Álvaro Herrera)
server failing to throw the required errors. !!! Note that this means existing databases with FKs that reference partitioned tables might have rows that break relational integrity, on tables that were once partitions on the referencing