| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Sebastian Böck <sebastianboeck(at)freenet(dot)de>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Bug with index-usage? |
| Date: | 2005-11-14 17:38:03 |
| Message-ID: | 1131989883.3582.8.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2005-11-14 at 11:30, Csaba Nagy wrote:
> The OP was complaining about the results of the above script, which I
> could readily reproduce on a 8.1.0 installation on debian (see below).
> The same select which returned 3 rows will return nothing after creating
> the partial indexes, which looks as a bug to me...
> I can't tell anything about why it happens, just confirm that I can
> reproduce too...
Yep, I just reproduced it too.
In the future, I'd recommend they include the bad output, as I simply
thought "unpredictable output" was referring to performance, not the
actual data.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sebastian Böck | 2005-11-14 18:06:02 | Re: Bug with index-usage? |
| Previous Message | Andreas Kretschmer | 2005-11-14 17:37:29 | Re: Bug with index-usage? |