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

From Tom Lane
Subject Re: Open issues for HOT patch
Date
Msg-id 25019.1190086374@sss.pgh.pa.us
Whole thread Raw
In response to Re: Open issues for HOT patch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Open issues for HOT patch
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: SPI access to PostgreSQL query plan
Next
From: Tom Lane
Date:
Subject: Re: SPI access to PostgreSQL query plan