Postgres Pro
Downloads
Home   >   mailing lists

Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing relation locking overhead) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing relation locking overhead)
Date
Msg-id 16021.1133901518@sss.pgh.pa.us
Whole thread Raw
In response to Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing  (Hannu Krosing <hannu@skype.net>)
Responses Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing
List pgsql-hackers
Tree view 
Hannu Krosing <hannu@skype.net> writes:
> What I have in mind would be something like this to get both SNAP2 and
> commit between any transactions:

> LOOP:
>     LOCK AGAINST STARTING NEW TRANSACTIONS

I can hardly credit that "let's block startup of ALL new transactions"
is a more desirable restriction than "let's block writers to the table
we wish to reindex".
        regards, tom lane

pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Slow email caught in the act
Next
From: Tom Lane
Date:
Subject: Re: Concurrent CREATE INDEX, try 2 (was Re: Reducing relation locking overhead)