Re: BUG #4618: nolock changes first column name of query result set to 'nolock' - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4618: nolock changes first column name of query result set to 'nolock'
Date
Msg-id 5832.1232117138@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #4618: nolock changes first column name of query result set to 'nolock'  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
Michael Fuhr <mike@fuhr.org> writes:
> On Fri, Jan 16, 2009 at 01:22:48PM +0100, Magnus Hagander wrote:
>> I don't know where you got "with (nolock)" from, but that's not
>> PostgreSQL syntax - and AFAIK it's not standard SQL at all. Just remove
>> it and you should be fine.

> "with (nolock)" is a SQL Server-ism for improving performance by
> using dirty reads.

Egad :-(.  All of a sudden I don't feel so bad about WITH becoming
a reserved word in 8.4.  At least we'll throw a syntax error for this
bit of silliness, instead of silently doing something that MSSQL
users won't expect.

Nonetheless, it was royally stupid of MS to adopt an extension
syntax that looks exactly like a table alias to a parser that
doesn't think that WITH is reserved.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_listener entries deleted under heavy NOTIFY load only on Windows
Next
From: Tom Lane
Date:
Subject: Re: BUG #4619: pg_ctl reports strange error message when be executed on non executable directory