Re: Tricky bugs in concurrent index build - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Tricky bugs in concurrent index build
Date
Msg-id 3456.1156528776@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tricky bugs in concurrent index build  ("Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
"Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at> writes:
>> That was what the patch originally used, but it was changed 
>> because it made difficult for psql to auto-complete that.

> That is imho not enough of a reason to divert.

My recollection is that the principal argument against ONLINE was
that it didn't convey the function of the option to anyone who
didn't already know Oracle's usage of the term.

Also, psql's problem is not with auto-completion, it's with
detecting whether the command is allowed inside a transaction
block.  That's not a function we can just blow off.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Tricky bugs in concurrent index build
Next
From: "Martin Atukunda"
Date:
Subject: Re: [PATCHES] psql 'none' as a HISTFILE special case