| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(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-19 18:25:16 |
| Message-ID: | 4E4EAA8C.4060408@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19.08.2011 21:06, Gokulakannan Somasundaram wrote:
> If you are following the same design that Heikki put forward, then there is
> a problem with it in maintaining the bits in page and the bits in visibility
> map in sync, which we have already discussed.
Are you referring to this:
http://archives.postgresql.org/pgsql-hackers/2010-02/msg02097.php ? I
believe Robert's changes to make the visibility map crash-safe covers
that. Clearing the bit in the visibility map now happens within the same
critical section as clearing the flag on the heap page and writing th
WAL record.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2011-08-19 18:51:09 | Re: the big picture for index-only scans |
| Previous Message | Tom Lane | 2011-08-19 18:13:11 | Rethinking sinval callback hook API |