| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Open issues for HOT patch |
| Date: | 2007-09-18 03:36:09 |
| Message-ID: | 200709180336.l8I3a9Q16840@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-18 03:38:41 | Re: Open issues for HOT patch |
| Previous Message | Tom Lane | 2007-09-18 03:35:30 | Re: SPI access to PostgreSQL query plan |