mirror of https://github.com/postgres/postgres
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.netpull/17/merge
parent
a8df75b0a4
commit
ff992c074e
@ -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'; |
@ -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'; |
Loading…
Reference in new issue