pg_restore -l documentation
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t75984psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 02:16 PM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t75984_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t75984_1 && git checkout t75984_1Patchset v1 (message #1) is on t75984_1
The docs for the -l switch in pg_restore say:
List the contents of the archive.
this is weird, because everywhere else we use "table of contents" to
describe this, which makes it seem like just plain 'contents' should mean
the bulk table data.
Attached patch changes it to say:
List the table of contents of the archive.
Cheers,
Jeff
On 8/3/17 15:56, Jeff Janes wrote:
The docs for the -l switch in pg_restore say:
List the contents of the archive.
this is weird, because everywhere else we use "table of contents" to
describe this, which makes it seem like just plain 'contents' should
mean the bulk table data.Attached patch changes it to say:
List the table of contents of the archive.
Committed, thanks!
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs