Re: Set AUTOCOMMIT to on in script output by pg_dump
Robert Treat <rob@xzilla.net>
From: Robert Treat <rob@xzilla.net>
To: Shinya Kato <Shinya11.Kato@oss.nttdata.com>
Cc: Yugo Nagata <nagata@sraoss.co.jp>,
"David G. Johnston" <david.g.johnston@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-17T15:45:46Z
Lists: pgsql-hackers
Attachments
- xzilla-pg_dump-no-psqlrc.diff (application/octet-stream) patch
On Thu, Oct 10, 2024 at 1:56 AM Shinya Kato <Shinya11.Kato@oss.nttdata.com> wrote: > Thank you all for the comments! <snip> > While adding to the documentation is sufficient if users use it > correctly, users often behave unexpectedly. My intention was to > implement it in a way that works without issues even if misused. > However, since the prevailing opinion seems to favor simply updating the > documentation, I will proceed with that approach. > > A new patch is attached. > I am not a native English, so corrections to the texts are welcome. > This looks pretty good to me. I think there are a couple of minor grammar changes that could be made, and I think the pg_dumpall section could use a couple tweaks, specifically 1) not all incantations of pg_dumpall emit psql meta commands (-g comes to mind quickly) and ISTR some non-psql clients honor psql meta commands, so I would lessen the language around incompatibility, and 2) I think adding an explicit -f for the database name in the pg_dumpall is clearer, and mirrors the pg_dump example. suggested diffs attached, let me know if you would like a consolidated patch Robert Treat https://xzilla.net
Commits
-
Doc: recommend "psql -X" for restoring pg_dump scripts.
- d83a108c10a3 18.0 landed
- c768f54a25a4 15.11 landed
- aaa0f061936a 13.19 landed
- 76601c0c885a 17.3 landed
- 53771e44df81 16.7 landed
- 4106942f004f 14.16 landed