From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
Cc: | Hannu Krosing <hannu(at)skype(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Another Idea: Try Including snapshot with TOAS (was: Including Snapshot Info with Indexes) |
Date: | 2007-10-13 06:43:33 |
Message-ID: | 1192257813.4233.594.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sat, 2007-10-13 at 11:12 +0530, Gokulakannan Somasundaram wrote:
> b) But i don't understand how storing the visibility info in TOAST
> table would help you. In that case you may need to update it for every
> delete/ update happening in the main table. Only thing, it would help
> is if someone wants to do a full table scan on TOAST table alone. May
> be Vacuum of TOAST tables can be done independently. But do you think
> it is worth the loss of performance in Update/Delete?
No
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-10-13 07:34:30 | Re: Seems we need a post-beta1 initdb already |
Previous Message | Gokulakannan Somasundaram | 2007-10-13 06:00:55 | Re: Including Snapshot Info with Indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-10-13 09:22:11 | Re: Including Snapshot Info with Indexes |
Previous Message | Gokulakannan Somasundaram | 2007-10-13 06:00:55 | Re: Including Snapshot Info with Indexes |