From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_dump vs. TRANSFORMs
Date: Wed, 11 May 2016 00:16:11 -0500
Message-ID: <04738f95-2dd4-0d8e-397a-e65720cab36f@BlueTreble.com> (raw)
In-Reply-To: <20160505133301.GN10850@tamriel.snowman.net>
References: <20160504183952.GE10850@tamriel.snowman.net>
<0a288671-29ec-ecdd-d8ae-e0f5c73dcc8d@2ndquadrant.com>
<15548.1462418615@sss.pgh.pa.us>
<376f5fb1-85cb-6b4c-9927-645b5e209456@2ndquadrant.com>
<20160505133301.GN10850@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 5/5/16 8:33 AM, Stephen Frost wrote:
> I strongly disagree with the idea that this is only an issue with the
> testing system. What if we add functions in the future that are
> created by initdb and *are* useful for transforms? What about casts?
> There are a lot of functions in pg_catalog that a user might wish to use
> to define their own cast. This also doesn't do anything about users
> creating functions in pg_catalog.
+1 to all of that. I know that I've at least created casts using
built-in functions during testing, and I think I might be doing it in
some of my extensions.
As for transforms, I suspect we're going to end up with some of those in
initdb in the future, because it's currently the only way you can
improve existing type transformations without breaking existing PL code.
--
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) mobile: 512-569-9461
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, sfrost@snowman.net, peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us
Subject: Re: pg_dump vs. TRANSFORMs
In-Reply-To: <04738f95-2dd4-0d8e-397a-e65720cab36f@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox