Subject: Re: pg_dump vs. TRANSFORMs
To: Stephen Frost <sfrost@snowman.net>, pgsql-hackers@postgresql.org
References: <20160504183952.GE10850@tamriel.snowman.net>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <0a288671-29ec-ecdd-d8ae-e0f5c73dcc8d@2ndquadrant.com>
Date: Wed, 4 May 2016 16:56:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <20160504183952.GE10850@tamriel.snowman.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 5/4/16 2:39 PM, Stephen Frost wrote:
> These checks are looking for the functions used by the transform in the
> list of functions that pg_dump has loaded, but in 9.5, we don't load any
> of the function in pg_catalog, and even with my patches, we only dump
> the functions in pg_catalog that have an ACL which has been changed from
> the default.

This issue is not specific to transforms.  For example, if you create a 
user-defined cast using a built-in function, the cast won't be dumped. 
Obviously, this is a problem, but it needs a more general solution.

-- 
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