Re: [HACKERS] Syntax of LOCK TABLE ...

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Vadim Mikheev <vadim(at)krasnet(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Sauer <davids(at)orfinet(dot)cz>, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] Syntax of LOCK TABLE ...
Date: 1999-05-17 14:08:35
Message-ID: 374022E3.BD889E2F@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I have modified the grammar to require IN. Looks like someone cleaned
> up the LOCK grammar options recently, but forgot the IN.

'Twas me. I don't recall seeing IN in the first place, but the
original gram.y support code did not actually use the normal yacc
grammar, but rather read most fields as IDENTS and then did strcmp()'s
to build the parse tree. There were lots of hidden behaviors in that.

Sorry, and thanks for fixing it.

- Tom

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 1999-05-17 14:08:45 Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)
Previous Message Oleg Bartunov 1999-05-17 14:00:27 Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)