| From: | Thomas Munro <munro(at)ip9(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: SKIP LOCKED DATA (work in progress) |
| Date: | 2014-05-23 18:01:01 |
| Message-ID: | CADLWmXV_mGV-vckE=yjke+4SopmemxJ8vC9m-y9s+nAKW+3aSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23 May 2014 15:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-05-23 18:59:24 | Re: Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3 |
| Previous Message | Amit Kapila | 2014-05-23 16:31:04 | Re: Wait free LW_SHARED acquisition - v0.2 |