Re: Change in "policy" on dump ordering?
Jim Nasby <jim.nasby@bluetreble.com>
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-22T23:24:49Z
Lists: pgsql-hackers
Attachments
- fix_dump_ordering.patch (text/plain) patch
On 2/22/17 12:29 PM, Peter Eisentraut wrote: > On 2/22/17 10:14, Jim Nasby wrote: >> CREATE MATERIALIZED VIEW tmv AS SELECT * FROM pg_subscription; >> SELECT 0 >> >> IOW, you can create matviews that depend on any other >> table/view/matview, but right now if the matview includes certain items >> it will mysteriously end up empty post-restore. > > Yes, by that logic matview refresh should always be last. Patches for head attached. RLS was the first item added after DO_REFRESH_MATVIEW, which was added in 9.5. So if we want to treat this as a bug, they'd need to be patched as well, which is a simple matter of swapping 33 and 34. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532)
Commits
-
Fix pg_dump/pg_restore to emit REFRESH MATERIALIZED VIEW commands last.
- b93217653b68 9.4.13 landed
- 65048cf23dba 9.5.8 landed
- 3d76328298ca 9.6.4 landed
- 3eb9a5e7c4c9 10.0 landed
- 035bb82222bc 9.3.18 landed