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 Raw
In response to Re: SKIP LOCKED DATA (work in progress)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<div dir="ltr">On 23 May 2014 15:40, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>>
wrote:<br/>> A different concern is that this patch adds not one but two new unreserved<br />> keywords, ie SKIP
andLOCKED.  That bloats our parser tables, which are<br /> > too darn large already, and it has a nonzero
compatibilitycost (since<br />> we only allow AS-less column aliases when they are no keyword at all).<br />> If
we'repulling syntax out of the air it'd be nice if we could avoid<br /> > adding new keywords to the grammar.<br
/> <br/>How about some of these combinations of existing words:<br /><br />EXCLUDE LOCK<br />NOWAIT EXCLUDE<br />NOWAIT
NEXT<br/>NOWAIT FOLLOWING<br />NOWAIT DISCARD<br /><br />Of those I think I prefer NOWAIT EXCLUDE (perhaps with NOWAIT
ABORTas a long version of the existing NOWAIT behaviour for contrast).<br /><br />Or adding just one new keyword:<br
/><br/>NOWAIT SKIP<br />SKIP LOCK<br /><br />Regards,<br />Thomas Munro</div> 

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