mirror of
https://github.com/postgres/postgres.git
synced 2026-03-09 09:40:40 -04:00
caddcb8f4b
This follows my proposal of yesterday, namely that we try to recreate the previous state of the extension exactly, instead of allowing CREATE EXTENSION to run a SQL script that might create some entirely-incompatible on-disk state. In --binary-upgrade mode, pg_dump won't issue CREATE EXTENSION at all, but instead uses a kluge function provided by pg_upgrade_support to recreate the pg_extension row (and extension-level pg_depend entries) without creating any member objects. The member objects are then restored in the same way as if they weren't members, in particular using pg_upgrade's normal hacks to preserve OIDs that need to be preserved. Then, for each member object, ALTER EXTENSION ADD is issued to recreate the pg_depend entry that marks it as an extension member. In passing, fix breakage in pg_upgrade's enum-type support: somebody didn't fix it when the noise word VALUE got added to ALTER TYPE ADD. Also, rationalize parsetree representation of COMMENT ON DOMAIN and fix get_object_address() to allow OBJECT_DOMAIN. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| check.c | ||
| controldata.c | ||
| dump.c | ||
| exec.c | ||
| file.c | ||
| function.c | ||
| IMPLEMENTATION | ||
| info.c | ||
| Makefile | ||
| option.c | ||
| page.c | ||
| pg_upgrade.c | ||
| pg_upgrade.h | ||
| relfilenode.c | ||
| server.c | ||
| tablespace.c | ||
| TESTING | ||
| util.c | ||
| version.c | ||
| version_old_8_3.c | ||