pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgbouncer - pgbouncer: sbuf.c: Fix connection hang if sbuf_loopcnt is
2+ messages / 2 participants
[nested] [flat]
* pgbouncer - pgbouncer: sbuf.c: Fix connection hang if sbuf_loopcnt is
@ 2009-06-25 14:18 User Mkz <mkz@pgfoundry.org>
0 siblings, 0 replies; 2+ messages in thread
From: mkz@pgfoundry.org @ 2009-06-25 14:18 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
sbuf.c: Fix connection hang if sbuf_loopcnt is set.
If query or result length nearby of multiple of (pktlen*sbuf_loopcnt)
[10k by default], it could stay waiting for more data which will not
appear.
Fix it by resyncing and final processing before exiting loop.
Modified Files:
--------------
pgbouncer/src:
sbuf.c (r1.35 -> r1.36)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/sbuf.c?r1=1.35&r2=1.36)
^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Add --copy-file-range option to pg_upgrade.
@ 2024-03-05 23:04 Thomas Munro <tmunro@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Munro @ 2024-03-05 23:04 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Add --copy-file-range option to pg_upgrade.
The copy_file_range() system call is available on at least Linux and
FreeBSD, and asks the kernel to use efficient ways to copy ranges of a
file. Options available to the kernel include sharing block ranges
(similar to --clone mode), and pushing down block copies to the storage
layer.
For automated testing, see PG_TEST_PG_UPGRADE_MODE. (Perhaps in a later
commit we could consider setting this mode for one of the CI targets.)
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Discussion: https://postgr.es/m/CA%2BhUKGKe7Hb0-UNih8VD5UNZy5-ojxFb3Pr3xSBBL8qj2M2%3DdQ%40mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/d93627bcbe5001750e7611f0e637200e2d81dcff
Modified Files
--------------
configure | 2 +-
configure.ac | 1 +
doc/src/sgml/ref/pgupgrade.sgml | 13 +++++++
meson.build | 1 +
src/bin/pg_upgrade/TESTING | 4 +-
src/bin/pg_upgrade/check.c | 3 ++
src/bin/pg_upgrade/file.c | 78 ++++++++++++++++++++++++++++++++++++++
src/bin/pg_upgrade/option.c | 7 +++-
src/bin/pg_upgrade/pg_upgrade.h | 4 ++
src/bin/pg_upgrade/relfilenumber.c | 8 ++++
src/include/pg_config.h.in | 3 ++
11 files changed, 120 insertions(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-03-05 23:04 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-06-25 14:18 pgbouncer - pgbouncer: sbuf.c: Fix connection hang if sbuf_loopcnt is User Mkz <mkz@pgfoundry.org>
2024-03-05 23:04 pgsql: Add --copy-file-range option to pg_upgrade. Thomas Munro <tmunro@postgresql.org>
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