From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Cc: | marko(at)joh(dot)to |
Subject: | Rethinking pg_dump's function sorting code |
Date: | 2015-03-06 00:28:33 |
Message-ID: | 5619.1425601713@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In bug #12832 Marko Tiikkaja points out that commit
7b583b20b1c95acb621c71251150beef958bb603 created a rather unnecessary
dump failure hazard, since it applies pg_get_function_identity_arguments()
to every function in the database, even those that won't get dumped.
I think we should fix this by getting rid of pg_dump's use of that
function altogether. A low-tech way to sort functions of identical names
would be to compare argument type OIDs, as in the attached simple patch.
If people feel it's important to avoid depending on numerical OID order,
we could instead look up type names locally and compare them as in the
attached less-simple patch. (Both patches neglect reverting the data
collection aspects of the prior commit, since that's mechanical; the only
interesting part is what we'll do to sort.)
Neither patch will exactly preserve the sort behavior of the current
code, but I don't think that's important.
Comments?
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
simple-function-argtype-sort.patch | text/x-diff | 1019 bytes |
less-simple-function-argtype-sort.patch | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-03-06 00:30:30 | Re: object description for FDW user mappings |
Previous Message | Amit Langote | 2015-03-06 00:22:13 | Re: object description for FDW user mappings |