pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feednpgsql - Npgsql2: Changed value of busy loop so it can stay longer.
2+ messages / 2 participants
[nested] [flat]
* npgsql - Npgsql2: Changed value of busy loop so it can stay longer.
@ 2009-07-06 14:38 User Fxjr <fxjr@pgfoundry.org>
0 siblings, 0 replies; 2+ messages in thread
From: fxjr@pgfoundry.org @ 2009-07-06 14:38 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Changed value of busy loop so it can stay longer.
Added outputparameter test function
Modified Files:
--------------
Npgsql2/testsuite/noninteractive:
add_functions.sql (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/testsuite/noninteractive/add_functions.sq...)
^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Keep replication slot statistics on invalidation
@ 2024-03-12 05:24 Michael Paquier <michael@paquier.xyz>
0 siblings, 0 replies; 2+ messages in thread
From: Michael Paquier @ 2024-03-12 05:24 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Keep replication slot statistics on invalidation
The code path in charge of invalidating a replication slot includes a
call to pgstat_drop_replslot(), which would result in removing the
statistics of the slot once invalidated. However, there is no need to
remove the statistics of an invalidated slot as one could still be
interested in looking at them to understand the activity of the slot
until its actual removal.
The initial design of the feature committed in be87200efd used the
approach to drop the slots, which is likely why the statistics were
still removed during the invalidation.
Another problem with this operation is that it was done without holding
ReplicationSlotAllocationLock, leaving it unprotected on concurrent
activity. This part is arguably a bug, but that's a limited problem in
practice so no backpatch is done.
In passing, this commit adds a test to check this behavior. The only
remaining code path where slot statistics are dropped now related to the
slot getting dropped.
Author: Bertrand Drouvot
Discussion: https://postgr.es/m/ZermH08Eq6YydHpO@ip-10-97-1-34.eu-west-3.compute.internal
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/d6e171fed6c56fc17405445951d5028b7c86a4e3
Modified Files
--------------
src/backend/replication/slot.c | 1 -
src/test/recovery/t/035_standby_logical_decoding.pl | 20 ++++++++++++++++++++
2 files changed, 20 insertions(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-03-12 05:24 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-07-06 14:38 npgsql - Npgsql2: Changed value of busy loop so it can stay longer. User Fxjr <fxjr@pgfoundry.org>
2024-03-12 05:24 pgsql: Keep replication slot statistics on invalidation Michael Paquier <michael@paquier.xyz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox