Postgres Pro
Downloads
Home   >   mailing lists

Re: CREATE INDEX and HOT - revised design - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CREATE INDEX and HOT - revised design
Date
Msg-id 3748.1175203634@sss.pgh.pa.us
Whole thread Raw
In response to Re: CREATE INDEX and HOT - revised design  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: CREATE INDEX and HOT - revised design  ("Florian G. Pflug" <fgp@phlo.org>)
Re: CREATE INDEX and HOT - revised design  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
Tree view 
"Simon Riggs" <simon@2ndquadrant.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.

Back to the drawing board :-(
        regards, tom lane

pgsql-hackers by date:

Previous
From: "Carlos Chacon"
Date:
Subject: timing in PostgreSQL
Next
From: "Florian G. Pflug"
Date:
Subject: Re: CREATE INDEX and HOT - revised design