Re: the big picture for index-only scans

From: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: the big picture for index-only scans
Date: 2011-08-24 10:19:57
Message-ID: CAHMh4-aZvpaA29tGbKtH9Dw6XS10KSXdj28f5OOcODS9VkybVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> There are extensive comments on this in visibilitymap.c and, in
> heapam.c, heap_xlog_visible().
>
> I went through the design again and again. I am convinced that this should
not have any functional bugs and should not cause much performance issues.
Nice thoughts on bypassing the WAL Logging.

Gokul.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dougal Sutherland 2011-08-24 11:33:54 patch to slightly improve clarity of a comment in postgresql.conf.sample
Previous Message Rushabh Lathia 2011-08-24 09:09:22 Windows env returns error while running "select pgstatindex"