pg_upgrade: Fix large object COMMENTS, SECURITY LABELS

When performing a pg_upgrade, we copy the files behind pg_largeobject
and pg_largeobject_metadata, allowing us to avoid having to dump out and
reload the actual data for large objects and their ACLs.

Unfortunately, that isn't all of the information which can be associated
with large objects.  Currently, we also support COMMENTs and SECURITY
LABELs with large objects and these were being silently dropped during a
pg_upgrade as pg_dump would skip everything having to do with a large
object and pg_upgrade only copied the tables mentioned to the new
cluster.

As the file copies happen after the catalog dump and reload, we can't
simply include the COMMENTs and SECURITY LABELs in pg_dump's binary-mode
output but we also have to include the actual large object definition as
well.  With the definition, comments, and security labels in the pg_dump
output and the file copies performed by pg_upgrade, all of the data and
metadata associated with large objects is able to be successfully pulled
forward across a pg_upgrade.

In 9.6 and master, we can simply adjust the dump bitmask to indicate
which components we don't want.  In 9.5 and earlier, we have to put
explciit checks in in dumpBlob() and dumpBlobs() to not include the ACL
or the data when in binary-upgrade mode.

Adjustments made to the privileges regression test to allow another test
(large_object.sql) to be added which explicitly leaves a large object
with a comment in place to provide coverage of that case with
pg_upgrade.

Back-patch to all supported branches.

Discussion: https://postgr.es/m/20170221162655.GE9812@tamriel.snowman.net

diff --git a/src/bin/pg_dump/pg_backup.h b/src/bin/pg_dump/pg_backup.h
index 4afa92f5f674328f74e784c15fe6a4a1334c3526..1641861f7ae4f63f3af1431fe4f97d1bc9406a23 100644 (file)
--- a/src/bin/pg_dump/pg_backup.h
+++ b/src/bin/pg_dump/pg_backup.h
@@ -117,6 +117,7 @@ typedef struct _restoreOptions
 
        bool       *idWanted;           /* array showing which dump IDs to emit */
        int                     enable_row_security;
+       int                     binary_upgrade;
 } RestoreOptions;
 
 typedef struct _dumpOptions

diff --git a/src/bin/pg_dump/pg_backup_archiver.c b/src/bin/pg_dump/pg_backup_archiver.c
index 9e9d11681aa0263fa682b4f9c37349677474a495..8f4b682406835e0982ce5f466fed7571ad9b337b 100644 (file)
--- a/src/bin/pg_dump/pg_backup_archiver.c
+++ b/src/bin/pg_dump/pg_backup_archiver.c
@@ -2842,7 +2842,17 @@ _tocEntryRequired(TocEntry *te, teSection curSection, RestoreOptions *ropt)
 
        /* Mask it if we only want schema */
        if (ropt->schemaOnly)
-               res = res & REQ_SCHEMA;
+       {
+               /*
+                * In binary-upgrade mode, even with schema-only set, we do not mask
+                * out large objects.  Only large object definitions, comments and
+                * other information should be generated in binary-upgrade mode (not
+                * the actual data).
+                */
+               if (!(ropt->binary_upgrade && strcmp(te->desc,"BLOB") == 0) &&
+               !(ropt->binary_upgrade && strncmp(te->tag,"LARGE OBJECT ", 13) == 0))
+                       res = res & REQ_SCHEMA;
+       }
 
        /* Mask it if we only want data */
        if (ropt->dataOnly)

diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c
index 2306735a5e21a38949a573358ab1b3cf9ba6bbf4..c15ac992065fa4dd74aa40c396494bd8e34db466 100644 (file)
--- a/src/bin/pg_dump/pg_dump.c
+++ b/src/bin/pg_dump/pg_dump.c
@@ -762,7 +762,15 @@ main(int argc, char **argv)
                        getTableDataFKConstraints();
        }
 
-       if (dopt.outputBlobs)
+       /*
+        * In binary-upgrade mode, we do not have to worry about the actual blob
+        * data or the associated metadata that resides in the pg_largeobject and
+        * pg_largeobject_metadata tables, respectivly.
+        *
+        * However, we do need to collect blob information as there may be
+        * comments or other information on blobs that we do need to dump out.
+        */
+       if (dopt.outputBlobs || dopt.binary_upgrade)
                getBlobs(fout);
 
        /*
@@ -845,6 +853,7 @@ main(int argc, char **argv)
        ropt->lockWaitTimeout = dopt.lockWaitTimeout;
        ropt->include_everything = dopt.include_everything;
        ropt->enable_row_security = dopt.enable_row_security;
+       ropt->binary_upgrade = dopt.binary_upgrade;
 
        if (compressLevel == -1)
                ropt->compression = 0;
@@ -2938,6 +2947,20 @@ getBlobs(Archive *fout)
                        PQgetisnull(res, i, i_initlomacl) &&
                        PQgetisnull(res, i, i_initrlomacl))
                        binfo[i].dobj.dump &= ~DUMP_COMPONENT_ACL;
+
+               /*
+                * In binary-upgrade mode for blobs, we do *not* dump out the data or
+                * the ACLs, should any exist.  The data and ACL (if any) will be
+                * copied by pg_upgrade, which simply copies the pg_largeobject and
+                * pg_largeobject_metadata tables.
+                *
+                * We *do* dump out the definition of the blob because we need that to
+                * make the restoration of the comments, and anything else, work since
+                * pg_upgrade copies the files behind pg_largeobject and
+                * pg_largeobject_metadata after the dump is restored.
+                */
+               if (dopt->binary_upgrade)
+                       binfo[i].dobj.dump &= ~(DUMP_COMPONENT_DATA | DUMP_COMPONENT_ACL);
        }
 
        /*
@@ -9103,7 +9126,8 @@ dumpComment(Archive *fout, const char *target,
        }
        else
        {
-               if (dopt->schemaOnly)
+               /* We do dump blob comments in binary-upgrade mode */
+               if (dopt->schemaOnly && !dopt->binary_upgrade)
                        return;
        }
 
@@ -14803,7 +14827,8 @@ dumpSecLabel(Archive *fout, const char *target,
        }
        else
        {
-               if (dopt->schemaOnly)
+               /* We do dump blob security labels in binary-upgrade mode */
+               if (dopt->schemaOnly && !dopt->binary_upgrade)
                        return;
        }
 

diff --git a/src/test/regress/expected/large_object.out b/src/test/regress/expected/large_object.out
new file mode 100644 (file)
index 0000000..b00d47c
--- /dev/null
+++ b/src/test/regress/expected/large_object.out
@@ -0,0 +1,15 @@
+-- This is more-or-less DROP IF EXISTS LARGE OBJECT 3001;
+WITH unlink AS (SELECT lo_unlink(loid) FROM pg_largeobject WHERE loid = 3001) SELECT 1;
+ ?column? 
+----------
+        1
+(1 row)
+
+-- Test creation of a large object and leave it for testing pg_upgrade
+SELECT lo_create(3001);
+ lo_create 
+-----------
+      3001
+(1 row)
+
+COMMENT ON LARGE OBJECT 3001 IS 'testing comments';

diff --git a/src/test/regress/expected/privileges.out b/src/test/regress/expected/privileges.out
index f66b4432a1567b162035ba9d8a91cb9d7eb96542..8ac46ecef2e57267f53165b958eaeb02230fb059 100644 (file)
--- a/src/test/regress/expected/privileges.out
+++ b/src/test/regress/expected/privileges.out
@@ -12,7 +12,7 @@ DROP ROLE IF EXISTS regress_user3;
 DROP ROLE IF EXISTS regress_user4;
 DROP ROLE IF EXISTS regress_user5;
 DROP ROLE IF EXISTS regress_user6;
-SELECT lo_unlink(oid) FROM pg_largeobject_metadata;
+SELECT lo_unlink(oid) FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
  lo_unlink 
 -----------
 (0 rows)
@@ -1173,11 +1173,11 @@ SELECT lo_unlink(2002);
 
 \c -
 -- confirm ACL setting
-SELECT oid, pg_get_userbyid(lomowner) ownername, lomacl FROM pg_largeobject_metadata;
+SELECT oid, pg_get_userbyid(lomowner) ownername, lomacl FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
  oid  |   ownername   |                                             lomacl                                             
 ------+---------------+------------------------------------------------------------------------------------------------
- 1002 | regress_user1 | 
  1001 | regress_user1 | {regress_user1=rw/regress_user1,=rw/regress_user1}
+ 1002 | regress_user1 | 
  1003 | regress_user1 | {regress_user1=rw/regress_user1,regress_user2=r/regress_user1}
  1004 | regress_user1 | {regress_user1=rw/regress_user1,regress_user2=rw/regress_user1}
  1005 | regress_user1 | {regress_user1=rw/regress_user1,regress_user2=r*w/regress_user1,regress_user3=r/regress_user2}
@@ -1546,7 +1546,7 @@ DROP TABLE atest6;
 DROP TABLE atestc;
 DROP TABLE atestp1;
 DROP TABLE atestp2;
-SELECT lo_unlink(oid) FROM pg_largeobject_metadata;
+SELECT lo_unlink(oid) FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
  lo_unlink 
 -----------
          1

diff --git a/src/test/regress/parallel_schedule b/src/test/regress/parallel_schedule
index 3815182fe7a8b14b3d89bd0d052ddc342aeb9939..0d68bcf9a4fa2863bc424e218c0a9807d7b8e942 100644 (file)
--- a/src/test/regress/parallel_schedule
+++ b/src/test/regress/parallel_schedule
@@ -84,7 +84,7 @@ test: select_into select_distinct select_distinct_on select_implicit select_havi
 # ----------
 # Another group of parallel tests
 # ----------
-test: brin gin gist spgist privileges init_privs security_label collate matview lock replica_identity rowsecurity object_address tablesample groupingsets drop_operator
+test: brin gin gist spgist privileges init_privs security_label collate matview lock replica_identity rowsecurity object_address tablesample groupingsets drop_operator large_object
 
 # ----------
 # Another group of parallel tests

diff --git a/src/test/regress/serial_schedule b/src/test/regress/serial_schedule
index 8958d8cdb9d29a46f6bc21a6b0069390794c41e1..17f1d855bcf2722daf63321974bce599abaca150 100644 (file)
--- a/src/test/regress/serial_schedule
+++ b/src/test/regress/serial_schedule
@@ -116,6 +116,7 @@ test: object_address
 test: tablesample
 test: groupingsets
 test: drop_operator
+test: large_object
 test: alter_generic
 test: alter_operator
 test: misc

diff --git a/src/test/regress/sql/large_object.sql b/src/test/regress/sql/large_object.sql
new file mode 100644 (file)
index 0000000..a9e18b7
--- /dev/null
+++ b/src/test/regress/sql/large_object.sql
@@ -0,0 +1,8 @@
+
+-- This is more-or-less DROP IF EXISTS LARGE OBJECT 3001;
+WITH unlink AS (SELECT lo_unlink(loid) FROM pg_largeobject WHERE loid = 3001) SELECT 1;
+
+-- Test creation of a large object and leave it for testing pg_upgrade
+SELECT lo_create(3001);
+
+COMMENT ON LARGE OBJECT 3001 IS 'testing comments';

diff --git a/src/test/regress/sql/privileges.sql b/src/test/regress/sql/privileges.sql
index 00dc7bd4ab203e54e834ba5b561e63fcbf9640ab..3d74abf043c628096d2bd3e71a9a2fbafc46da59 100644 (file)
--- a/src/test/regress/sql/privileges.sql
+++ b/src/test/regress/sql/privileges.sql
@@ -17,7 +17,7 @@ DROP ROLE IF EXISTS regress_user4;
 DROP ROLE IF EXISTS regress_user5;
 DROP ROLE IF EXISTS regress_user6;
 
-SELECT lo_unlink(oid) FROM pg_largeobject_metadata;
+SELECT lo_unlink(oid) FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
 
 RESET client_min_messages;
 
@@ -729,7 +729,7 @@ SELECT lo_unlink(2002);
 
 \c -
 -- confirm ACL setting
-SELECT oid, pg_get_userbyid(lomowner) ownername, lomacl FROM pg_largeobject_metadata;
+SELECT oid, pg_get_userbyid(lomowner) ownername, lomacl FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
 
 SET SESSION AUTHORIZATION regress_user3;
 
@@ -960,7 +960,7 @@ DROP TABLE atestc;
 DROP TABLE atestp1;
 DROP TABLE atestp2;
 
-SELECT lo_unlink(oid) FROM pg_largeobject_metadata;
+SELECT lo_unlink(oid) FROM pg_largeobject_metadata WHERE oid >= 1000 AND oid < 3000 ORDER BY oid;
 
 DROP GROUP regress_group1;
 DROP GROUP regress_group2;