Re: SKIP LOCKED DATA (work in progress)
| От | Thomas Munro |
|---|---|
| Тема | Re: SKIP LOCKED DATA (work in progress) |
| Дата | |
| Msg-id | CADLWmXV_mGV-vckE=yjke+4SopmemxJ8vC9m-y9s+nAKW+3aSA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: SKIP LOCKED DATA (work in progress) (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | 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 по дате отправления: