Re: pg_dump no-owner option
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: borisnov@acm.org
Cc: pgsql-docs@lists.postgresql.org
Date: 2021-01-13T17:54:20Z
Lists: pgsql-docs
PG Doc comments form <noreply@postgresql.org> writes: > Currently the documentation reads: > This option is only meaningful for the plain-text format. > This statement is imprecise. Yeah, I agree --- it's not clear whether the option is ignored or rejected. Explicitly saying it's ignored is an improvement. > Would be much better to change the behavior of the utility to allow the > option for all formats, but htis is somewhat more than just documentaion > change. I disagree that that would be an improvement. Per the next sentence that you omitted, the right time to apply this and similar options is when extracting data from the archive format. (pg_dump to text effectively constructs an archive dump in-memory and then extracts from that, so that its "back half" logic is identical to pg_restore's.) Filtering this info before dumping the archive would save no meaningful amount of space, while restricting how the archive could be used later. regards, tom lane
Commits
-
Doc: clarify behavior of back-half options in pg_dump.
- c77f31171c83 13.2 landed
- bcdff449145a 11.11 landed
- 89160369ec8b 10.16 landed
- 7343a1559251 9.6.21 landed
- 2d19f13773ca 9.5.25 landed
- 06ed235adeb6 14.0 landed
- 0363b7e908cd 12.6 landed