| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GIN indexscans versus equality selectivity estimation |
| Date: | 2011-01-10 01:06:14 |
| Message-ID: | 4D2A5B86.8090502@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/9/11 3:38 PM, Tom Lane wrote:
> 1. Do nothing. The issue seems quite unlikely to affect anyone in the
> field, since in fact "use a seqscan" is probably the right answer
> anytime reltuples = 1; and anyway using a GIN index for plain equality
> is a corner case to begin with. However, it could confuse people who
> were doing testing (it confused me!).
+1. It's an unexpected result, but not actually a bad one. It just
doesn't seem worth messing with code which works in production just to
help testing.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-10 01:27:58 | Re: Compatibility GUC for serializable |
| Previous Message | Tom Lane | 2011-01-10 00:47:46 | Re: Compatibility GUC for serializable |