Re: ERROR: GIN indexes do not support whole-index scans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Flanagan" <kevin-f(at)linkprior(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: GIN indexes do not support whole-index scans
Date: 2010-05-20 21:15:28
Message-ID: 8825.1274390128@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Flanagan" <kevin-f(at)linkprior(dot)com> writes:
> Why would adding "target_lang_code='en'" cause this error?

Hard to tell without seeing the index definitions for this table.
Also could we see the EXPLAIN plans for both queries? (If possible
... I'm not sure whether you'd get this error just from EXPLAINing
the problem query.)

> Environment: PostgreSQL 8.4 on Windows (installed with one-click installer),

8.4.what-exactly?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-05-20 21:19:42 Re: Unexpected data beyond EOF during heavy writes
Previous Message Tony Sullivan 2010-05-20 20:54:17 Re: Unexpected data beyond EOF during heavy writes