pg_dump: Fix ordering
Materialized views refresh should be last. From: Jim Nasby <Jim.Nasby@BlueTreble.com>
This commit is contained in:
parent
272adf4f9c
commit
d77ff69341
@ -26,6 +26,9 @@ static const char *modulename = gettext_noop("sorter");
|
|||||||
* Sort priority for database object types.
|
* Sort priority for database object types.
|
||||||
* Objects are sorted by type, and within a type by name.
|
* Objects are sorted by type, and within a type by name.
|
||||||
*
|
*
|
||||||
|
* Because materialized views can potentially reference system views,
|
||||||
|
* DO_REFRESH_MATVIEW should always be the last thing on the list.
|
||||||
|
*
|
||||||
* NOTE: object-type priorities must match the section assignments made in
|
* NOTE: object-type priorities must match the section assignments made in
|
||||||
* pg_dump.c; that is, PRE_DATA objects must sort before DO_PRE_DATA_BOUNDARY,
|
* pg_dump.c; that is, PRE_DATA objects must sort before DO_PRE_DATA_BOUNDARY,
|
||||||
* POST_DATA objects must sort after DO_POST_DATA_BOUNDARY, and DATA objects
|
* POST_DATA objects must sort after DO_POST_DATA_BOUNDARY, and DATA objects
|
||||||
@ -70,11 +73,11 @@ static const int dbObjectTypePriority[] =
|
|||||||
22, /* DO_PRE_DATA_BOUNDARY */
|
22, /* DO_PRE_DATA_BOUNDARY */
|
||||||
26, /* DO_POST_DATA_BOUNDARY */
|
26, /* DO_POST_DATA_BOUNDARY */
|
||||||
33, /* DO_EVENT_TRIGGER */
|
33, /* DO_EVENT_TRIGGER */
|
||||||
34, /* DO_REFRESH_MATVIEW */
|
38, /* DO_REFRESH_MATVIEW */
|
||||||
35, /* DO_POLICY */
|
34, /* DO_POLICY */
|
||||||
36, /* DO_PUBLICATION */
|
35, /* DO_PUBLICATION */
|
||||||
37, /* DO_PUBLICATION_REL */
|
36, /* DO_PUBLICATION_REL */
|
||||||
38 /* DO_SUBSCRIPTION */
|
37 /* DO_SUBSCRIPTION */
|
||||||
};
|
};
|
||||||
|
|
||||||
static DumpId preDataBoundId;
|
static DumpId preDataBoundId;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user