Stephen Frost <sfr...@snowman.net> writes:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
>> Since we've fixed a couple of relatively nasty bugs recently, the core
>> committee has determined that it'd be a good idea to push out PG update
>> releases soon.  The current plan is to wrap on Monday Feb 4 for public
>> announcement Thursday Feb 7.  If you're aware of any bug fixes you think
>> ought to get included, now's the time to get them done ...

> Should we consider including Simon's fix for an issue which Noah noted
> in this thread?:
> http://www.postgresql.org/message-id/CA+U5nMKBrqFxyohr=JSDpgxZ6y0nfAdmt=k3hk4zzfqo1mh...@mail.gmail.com

It sounds like there's something to fix there, but AFAICS the thread is
still arguing about the best fix.  There's time to do it non-hastily.

                        regards, tom lane


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

Reply via email to