Maxim Boguk writes:
> Is that fix will be included to the next minor versions releases?
Yes, it's in already:
http://git.postgresql.org/gitweb/?p=postgresql.git
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
On Mon, Nov 28, 2011 at 6:02 PM, Simon Riggs wrote:
> On Fri, Nov 25, 2011 at 6:33 PM, Tom Lane wrote:
> > Maxim Boguk writes:
> >> I know GIST on intarray[] do not have that problem.
> >> Very likely the problem is limited to intarray[] GIN indexes only
> >> (but I going to test some other not
On Fri, Nov 25, 2011 at 6:33 PM, Tom Lane wrote:
> Maxim Boguk writes:
>> I know GIST on intarray[] do not have that problem.
>> Very likely the problem is limited to intarray[] GIN indexes only
>> (but I going to test some other not-well known GIN indexes tomorrow).
>
>> Broken FTS indexes on Ho
Maxim Boguk writes:
> I know GIST on intarray[] do not have that problem.
> Very likely the problem is limited to intarray[] GIN indexes only
> (but I going to test some other not-well known GIN indexes tomorrow).
> Broken FTS indexes on Hot Standby should be known years before.
You might think
On Fri, Nov 25, 2011 at 11:17 PM, Simon Riggs wrote:
> On Thu, Nov 24, 2011 at 11:12 PM, Maksym Boguk
> wrote:
>
> > postgres=# SELECT * from test where sections && '{2000}';
> > id | sections
> > +--
> > (0 rows)
> >
> > Ooops.
>
> Can you see if this is just intarray or if there a
On Thu, Nov 24, 2011 at 11:12 PM, Maksym Boguk wrote:
> postgres=# SELECT * from test where sections && '{2000}';
> id | sections
> +--
> (0 rows)
>
> Ooops.
Can you see if this is just intarray or if there are other failing cases?
It would be good to get more info on this before I
The following bug has been logged online:
Bug reference: 6307
Logged by: Maksym Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Linux
Description:intarray extention gin index does not work with Hot
standby
Details:
Intarray gin
