Re: SKIP LOCKED DATA (work in progress) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: SKIP LOCKED DATA (work in progress)
Date
Msg-id CADLWmXV_mGV-vckE=yjke+4SopmemxJ8vC9m-y9s+nAKW+3aSA@mail.gmail.com
Whole thread
In response to Re: SKIP LOCKED DATA (work in progress)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 23 May 2014 15:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> A different concern is that this patch adds not one but two new unreserved
> keywords, ie SKIP and LOCKED.  That bloats our parser tables, which are
> too darn large already, and it has a nonzero compatibility cost (since
> we only allow AS-less column aliases when they are no keyword at all).
> If we're pulling syntax out of the air it'd be nice if we could avoid
> adding new keywords to the grammar.
 
How about some of these combinations of existing words:

EXCLUDE LOCK
NOWAIT EXCLUDE
NOWAIT NEXT
NOWAIT FOLLOWING
NOWAIT DISCARD

Of those I think I prefer NOWAIT EXCLUDE (perhaps with NOWAIT ABORT as a long version of the existing NOWAIT behaviour for contrast).

Or adding just one new keyword:

NOWAIT SKIP
SKIP LOCK

Regards,
Thomas Munro

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Wait free LW_SHARED acquisition - v0.2
Next
From: Bruce Momjian
Date:
Subject: Re: Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3