pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedjsonpath - postgresql-json: First commit.
2+ messages / 2 participants
[nested] [flat]
* jsonpath - postgresql-json: First commit.
@ 2009-06-01 09:58 User Marian <marian@pgfoundry.org>
0 siblings, 0 replies; 2+ messages in thread
From: marian@pgfoundry.org @ 2009-06-01 09:58 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
First commit.
Added Files:
-----------
postgresql-json/src:
postgres_json.sql (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/postgres_json.sql?rev=1.1&a...)
postgres_json_test.sql (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/postgres_json_test.sql?rev=...)
postgres_json_drop.sql (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/postgres_json_drop.sql?rev=...)
Makefile (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/Makefile?rev=1.1&conten...)
postgres_json.c (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/postgres_json.c?rev=1.1&...)
README (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/src/README?rev=1.1&content-...)
postgresql-json:
.project (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jsonpath/postgresql-json/.project?rev=1.1&content-ty...)
^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Fix unnecessary padding in incremental backups
@ 2024-04-14 18:38 Tomas Vondra <tomas.vondra@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Tomas Vondra @ 2024-04-14 18:38 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Fix unnecessary padding in incremental backups
Commit 10e3226ba13d added padding to incremental backups to ensure the
block data is properly aligned. The code in sendFile() however failed to
consider that the header may be a multiple of BLCKSZ and thus already
aligned, adding a full BLCKSZ of unnecessary padding.
Not only does this make the incremental file a bit larger, but the other
places calculating the amount of padding did realize it's not needed and
did not include it in the formula. This resulted in pg_basebackup
getting confused while parsing the data stream, trying to access files
with invalid filenames (e.g. with binary data etc.) and failing.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/cd4b6af620975bb9802c464a06d2289d2f97cbf4
Modified Files
--------------
src/backend/backup/basebackup.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-04-14 18:38 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-06-01 09:58 jsonpath - postgresql-json: First commit. User Marian <marian@pgfoundry.org>
2024-04-14 18:38 pgsql: Fix unnecessary padding in incremental backups Tomas Vondra <tomas.vondra@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