Re: [PATCH] pg_dump: Sort overloaded functions in deterministic order - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: [PATCH] pg_dump: Sort overloaded functions in deterministic order
Date
Msg-id CAASwCXdtEWWGzX=Egw--prWcWaoj_EYMBiwMC161XBxHsicT_g@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pg_dump: Sort overloaded functions in deterministic order  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] pg_dump: Sort overloaded functions in deterministic order  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I agree, good suggestion, I just didn't know how to implement it without a new field. I'll make a new attempt to get it right.

On Thursday, July 5, 2012, Tom Lane wrote:
Joel Jacobson <joel@trustly.com> writes:
> New version, made a typo in last one.

I'm not particularly happy with the idea of adding a sortkey field to
DumpableObject as such, when most object types don't need it.  That just
bloats the code and pg_dump's memory consumption.  It would be better to
modify the already-existing object-type-specific special cases in
DOTypeNameCompare to take additional information into account as needed.

BTW, I see no reason to be adding extra calls of
pg_get_function_identity_arguments.  What is wrong with the funcsig or
aggsig strings that the code already computes?

                        regards, tom lane

pgsql-hackers by date:

Previous
From: John Lumby
Date:
Subject: Re: proposal and patch : support INSERT INTO...RETURNING with partitioned table using rule
Next
From: Heikki Linnakangas
Date:
Subject: Re: plpython issue with Win64 (PG 9.2)