Subject: Re: Change in "policy" on dump ordering?
To: Jim Nasby <Jim.Nasby@BlueTreble.com>,
 Pg Hackers <pgsql-hackers@postgresql.org>
References: <87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com>
 <8f64786e-824d-7c0d-33a6-3d9e1c8e9fde@2ndquadrant.com>
 <edc1dc0d-66ba-0d9e-b0e7-890f064789d7@BlueTreble.com>
 <33b25c65-94f1-6ff6-c717-61a56294a255@2ndquadrant.com>
 <a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com>
 <75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com>
 <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com>
 <67d35333-ef65-074a-b2be-52440f245e43@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <753dcafc-a648-9041-e9ca-e405cd4498f4@2ndquadrant.com>
Date: Sat, 4 Mar 2017 14:49:36 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <67d35333-ef65-074a-b2be-52440f245e43@2ndquadrant.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 3/1/17 08:36, Peter Eisentraut wrote:
> On 2/22/17 18:24, Jim Nasby wrote:
>>> 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?

Since there wasn't any interest in that idea, I have committed Jim's
patch as is.

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers