From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Andres Freund <andres(at)anarazel(dot)de> |
Subject: | pg_dump/restore --no-tableam |
Date: | 2021-12-07 15:39:30 |
Message-ID: | 20211207153930.GR17618@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I first suggested this a couple years ago.
Is it desirable to implement in pg_dump and pg_restore ?
It'd be just like --tablespace.
On Tue, Jan 28, 2020 at 07:33:17AM -0600, Justin Pryzby wrote:
> I made these casual comments. If there's any agreement on their merit, it'd be
> nice to implement at least the first for v13.
>
> In <20190818193533(dot)GL11185(at)telsasoft(dot)com>, I wrote:
> > . What do you think about pg_restore --no-tableam; similar to
> > --no-tablespaces, it would allow restoring a table to a different AM:
> > PGOPTIONS='-c default_table_access_method=zedstore' pg_restore --no-tableam ./pg_dump.dat -d postgres
> > Otherwise, the dump says "SET default_table_access_method=heap", which
> > overrides any value from PGOPTIONS and precludes restoring to new AM.
>
> That appears to be a trivial variation on no-tablespace:
>
> /* do nothing in --no-tablespaces mode */
> if (ropt->noTablespace)
> return;
...
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-12-07 15:45:55 | Re: Is there any documentation on how to correctly create extensions in HA(primary-standby) setup? |
Previous Message | Peter Eisentraut | 2021-12-07 15:39:29 | Re: Transparent column encryption |