Re: Open issues for HOT patch - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Open issues for HOT patch
Date
Msg-id 200709180336.l8I3a9Q16840@momjian.us
Whole thread Raw
In response to Re: Open issues for HOT patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Open issues for HOT patch
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > If we only prune on an update (or insert) why not just do prune every
> > time?
> 
> The problem is you can't prune anymore once you have existing pin on the
> target page.  I'd really like to get around that, but so far it seems
> unacceptably fragile --- the executor really doesn't expect tuples to
> get moved around underneath it.

I thought you could do the pruning before you pin the page only in
update/insert cases.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SPI access to PostgreSQL query plan
Next
From: Tom Lane
Date:
Subject: Re: Open issues for HOT patch