From: Tom Lane on
"David E. Wheeler" <david(a)kineticode.com> writes:
> FWIW, I think that this is a bug, and that the variation from the text
> version will be unexpected. I recommend fixing it for 8.4.2.

Well, it's certainly a bug, but I don't think it's back-patchable.
A back-patch will not affect existing installations anyway. What it
will do is break user code that is expecting the existing behavior
(for instance, Rod's index). I think it's something we can only
change at a major version boundary.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on
"David E. Wheeler" <david(a)kineticode.com> writes:
> Is there a straight-foward way to check such a thing
> programmatically, with a query perhaps? Or should I just put aside an
> hour to do an audit?

I was wondering whether you could query pg_proc to look for functions
with the same name and different arguments/results. It's a bit tricky
though because you'd expect s/citext/text/ in at least some positions
(maybe not all)?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "David E. Wheeler" on
On Oct 21, 2009, at 9:48 AM, Tom Lane wrote:

> I was wondering whether you could query pg_proc to look for functions
> with the same name and different arguments/results. It's a bit tricky
> though because you'd expect s/citext/text/ in at least some positions
> (maybe not all)?

Yeah, almost all. I'll poke around, though it might be a day or two…

Best,

David
--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers