Re: pg_dump/restore --no-tableam
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org, Andres Freund <andres@anarazel.de>
Date: 2022-01-17T05:55:58Z
Lists: pgsql-hackers
On Tue, Jan 11, 2022 at 10:09:07PM -0600, Justin Pryzby wrote: > I suppose you're right - I had previously renamed it from no-tableam. Thanks for the new version. I have noticed that support for the option with pg_dumpall was missing, but that looks useful to me like the other switches. > Because it looks like this is intended to be mostly alphabetical, but that > wasn't preserved by 63db0ac3f. It's most apparent in "my %full_runs". Sure. Now I am not sure that this is worth poking at if we don't change the back-branches, as this could cause conflicts. So I have left this change out at the end. And, done. -- Michael
Commits
-
Fix typo in pg_dumpall.c
- ca86a63d207a 15.0 landed
-
Add support for --no-table-access-method in pg_{dump,dumpall,restore}
- 2158628864cf 15.0 landed