| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Visibility map thoughts |
| Date: | 2007-11-06 14:08:37 |
| Message-ID: | 1194358117.4268.44.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2007-11-06 at 13:29 +0000, Heikki Linnakangas wrote:
> > My list would be:
> > - EXISTS / NOT EXISTS
> > - COUNT(*)
>
> Yeah, those are good candidates.
Yeah.
> Many-to-many relationships is one example:
OK, thats a very good one.
> And of course people will start adding columns to indexes, to make use
> of index-only-scans, once we have the capability.
Not too keen on that. Very difficult to judge whether its worth the
benefit for creating lots of extra columns in indexes. Specifically,
this isn't going to speed up any existing application without additional
design work.
But seems like we have reasonable reason for them without that.
Do we know how much faster things might go if we do that?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-11-06 14:18:21 | Re: Visibility map thoughts |
| Previous Message | Heikki Linnakangas | 2007-11-06 13:52:58 | Re: Visibility map thoughts |