diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-01-17 14:51:46 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-01-17 14:51:46 +0900 |
| commit | 2158628864cfbc03c838834a46c193bde5807361 (patch) | |
| tree | b51144b680bad500b57eaa7b9a95165107705cc3 /src/backend/nodes/nodeFuncs.c | |
| parent | f47ed79cc8a0cfa154dc7f01faaf59822552363f (diff) | |
| download | postgresql-2158628864cfbc03c838834a46c193bde5807361.tar.gz postgresql-2158628864cfbc03c838834a46c193bde5807361.zip | |
Add support for --no-table-access-method in pg_{dump,dumpall,restore}
The logic is similar to default_tablespace in some ways, so as no SET
queries on default_table_access_method are generated before dumping or
restoring an object (table or materialized view support table AMs) when
specifying this new option.
This option is useful to enforce the use of a default access method even
if some tables included in a dump use an AM different than the system's
default.
There are already two cases in the TAP tests of pg_dump with a table and
a materialized view that use a non-default table AM, and these are
extended that the new option does not generate SET clauses on
default_table_access_method.
Author: Justin Pryzby
Discussion: https://postgr.es/m/20211207153930.GR17618@telsasoft.com
Diffstat (limited to 'src/backend/nodes/nodeFuncs.c')
0 files changed, 0 insertions, 0 deletions