From: Jim Nasby <jim.nasby@openscg.com>
Subject: Re: Change in "policy" on dump ordering?
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.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>
 <753dcafc-a648-9041-e9ca-e405cd4498f4@2ndquadrant.com>
Message-ID: <bcad6d9c-ef3c-9668-ff54-9900955a7b6d@openscg.com>
Date: Sun, 5 Mar 2017 13:12:13 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <753dcafc-a648-9041-e9ca-e405cd4498f4@2ndquadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 3/4/17 11:49 AM, Peter Eisentraut wrote:
>> 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.

Thanks. Something else that seems somewhat useful would be to have the 
sort defined by an array of the ENUM values in the correct order, and 
then have the code do the mechanical map generation. I'm guessing the 
only reasonable way to make that work would be to have some kind of a 
last item indicator value, so you know how many values were in the ENUM. 
Maybe there's a better way to do that...
-- 
Jim Nasby, Chief Data Architect, OpenSCG


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