Re: Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index

From: "Burgess, Freddie" <FBurgess(at)Radiantblue(dot)com>
To: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index
Date: 2014-05-12 17:30:13
Message-ID: 3BBE635F64E28D4C899377A61DAA9FE01B9C6505@NBSVR-MAIL01.radiantblue.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

We will likely run into this bug at our shop, any idea when the official patch for this condition will be released?

Thanks

Freddie

________________________________
From: pgsql-bugs-owner(at)postgresql(dot)org [pgsql-bugs-owner(at)postgresql(dot)org] on behalf of narupley__ [nickr(at)mirthcorp(dot)com]
Sent: Tuesday, May 06, 2014 10:41 AM
To: pgsql-bugs(at)postgresql(dot)org
Subject: [BUGS] Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index

Alvaro Herrera-9 wrote
There's also the nightly snapshots, ftp://ftp.postgresql.org/pub/snapshot/9.3 which are pretty much equivalent to the release tarballs in that they don't require you to have bison, flex and other development tools.
We do always build from source anyway, so the nightly snapshot should work out just fine. Thanks again for all the help guys!
________________________________
View this message in context: Re: BUG #10189: Limit in 9.3.4 no longer works when ordering using a composite multi-type index<http://postgresql.1045698.n5.nabble.com/BUG-10189-Limit-in-9-3-4-no-longer-works-when-ordering-using-a-composite-multi-type-index-tp5802079p5802704.html>
Sent from the PostgreSQL - bugs mailing list archive<http://postgresql.1045698.n5.nabble.com/PostgreSQL-bugs-f2117394.html> at Nabble.com.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message sidharthdeshpande 2014-05-12 23:46:23 BUG #10297: yum - transaction check error
Previous Message Pavel Stehule 2014-05-12 14:50:40 Re: BUG #10294: DROP DOMAIN IF EXISTS does not work as expected if schema does not exist also