-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If it gives right answers after you increase work_mem sufficiently,
> I'd bet on this one ...
That's a good bet. Changing it from 1024 to 3500 did the trick ... only
one row returned, even when using the index. Thanks very much!
- --
Greg Sabino
Greg Sabino Mullane <[EMAIL PROTECTED]> writes:
> I could not duplicate this on any identical database, but thought I
> would report it here, just for completeness. I've tried reindexing,
> vacuuming, etc. Explain plans all look normal.
Possibly explained by this 8.1.4 fix?
2006-05-18 14:57 tgl
I could not duplicate this on any identical database, but thought I
would report it here, just for completeness. I've tried reindexing,
vacuuming, etc. Explain plans all look normal.
Version is 8.1.3
\d bigtable
...
"bigtable_status_partial" btree (status) WHERE status::text <>
'shipped'::text
The following bug has been logged online:
Bug reference: 2595
Logged by: Gin Indexes cause server to crash on Windows
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2 CVS-Aug 28
Operating system: Windows XP Pro
Description:Gin Indexes cause server to crash on