Re: [HACKERS] Change in "policy" on dump ordering? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Change in "policy" on dump ordering?
Date
Msg-id 67d35333-ef65-074a-b2be-52440f245e43@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Change in "policy" on dump ordering?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Change in "policy" on dump ordering?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2/22/17 18:24, Jim Nasby wrote:
> 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.

I wonder whether we should emphasize this change by assigning
DO_REFRESH_MATVIEW a higher number, like 100?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: [HACKERS] Patch to improve performance of replay of AccessExclusiveLock
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] \h tab-completion