From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Vadim Mikheev <vadim(at)krasnet(dot)ru> |
Cc: | 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 00:22:19 |
Message-ID: | 199905170022.UAA17362@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tom Lane wrote:
> >
> > David Sauer <davids(at)orfinet(dot)cz> writes:
> > > => lock table t row share mode;
> > > LOCK TABLE
> > > ... this works
> > > but:
> > > => lock table t IN row share mode;
> > > ERROR: parser: parse error at or near "in"
> > > .... but this not
> >
> > > It is mistake in grammar, or is there all OK ?
> >
> > I see this behavior too, and a quick look at gram.y shows that indeed
> > it is not expecting IN in a LOCK statement. I do not know whether the
> > standard permits (or requires?) the IN keyword, so I don't know whether
> > to make the change...
>
> IN is required...
I have modified the grammar to require IN. Looks like someone cleaned
up the LOCK grammar options recently, but forgot the IN.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-05-17 00:29:41 | sgmr* vs. md* |
Previous Message | Oleg Bartunov | 1999-05-16 21:47:56 | Re: [HACKERS] How good is FreeBSD for postgres ? |