Re: CREATE INDEX and HOT - revised design

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Pavan Deolasee <pavan(dot)deolasee(at)enterprisedb(dot)com>
Subject: Re: CREATE INDEX and HOT - revised design
Date: 2007-03-29 21:48:34
Message-ID: 460C3432.6000209@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
>> ISTM that the run-another-transaction-afterwards idea is the only one
>> that does everything I think we need. I really do wish we could put in a
>> wait, like CIC, but I just think it will break existing programs.
>
> Actually, there's a showstopper objection to that: plain CREATE INDEX
> has to be able to run within a larger transaction. (To do otherwise
> breaks "pg_dump --single-transaction", just for starters.) This means
> it can *not* commit partway through.

I believe the original idea was to invent some kind of "on commit run
this transaction" hook - similar to how files are deleted on commit,
I think. At least I understood the "Run another transaction on commit"
that way...

greetings, Florian Pflug

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-03-29 21:59:52 List of uncompleted patches for 8.2
Previous Message Tom Lane 2007-03-29 21:27:14 Re: CREATE INDEX and HOT - revised design