Re: pg_dump sort order for functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump sort order for functions
Date
Msg-id 3503.1263307495@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump sort order for functions  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_dump sort order for functions  (Magnus Hagander <magnus@hagander.net>)
Re: pg_dump sort order for functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On mån, 2010-01-11 at 12:54 -0500, Tom Lane wrote:
>> -- Name: binary_coercible(oid, oid); Type: FUNCTION; Schema: public; Owner: postgres

> Um, that tag is the "name", and if you change that, the name in CREATE
> FUNCTION also changes.

So?

> In the mean time, hacking it into the sort function itself as a special
> case works out fine, per attached patch.  One might frown upon such an
> exception, but then again, function overloading is an exception to the
> one-name-per-object rule all over the place anyway. ;-)

No, that's a completely bogus solution, because it depends on type
OIDs.  It won't be stable across dump/reload, which defeats the purpose
AFAICS.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: Typed tables
Next
From: Magnus Hagander
Date:
Subject: Re: pg_dump sort order for functions