On Wed, Feb 24, 2010 at 10:58:17PM -0500, Tom Lane wrote: > Alex Hunsaker <[email protected]> writes: > > On Wed, Feb 24, 2010 at 20:37, Alex Hunsaker <[email protected]> wrote: > >> On Wed, Feb 24, 2010 at 20:19, Tom Lane <[email protected]> wrote: > >>> Seems entirely unacceptable. > > >> I think we will see if we can get this fixed on the Safe/perl side then. > > > BTW the trade off here is we revert back to sort { $a <=> $b } not > > working. That is if you could call it a trade off... The level of > > breaking is not really comparable :) > > That's two unacceptable alternatives, you need to find a third one. > I think most people will have no trouble settling on "do not update > to Safe 2.2x" if you don't offer a better solution than these.
I believe the next version of Safe will revert to Safe 1.19 behaviour because the side effects of the change in 2.20 are too severe for it to be left enabled by default. Tim. -- Sent via pgsql-bugs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
