Re: LOCK for non-tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: LOCK for non-tables
Date
Msg-id 10862.1295037975@sss.pgh.pa.us
Whole thread Raw
In response to Re: LOCK for non-tables  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: LOCK for non-tables  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Fri, 2011-01-14 at 15:05 -0500, Tom Lane wrote:
>> No, that will not work at all.  LOCK has to be a utility command.

> But it doesn't break the use case for locking sequences, ISTM.

You haven't stated what you think that use case is, but in any case
I'm sure someone can come up with another one where not freezing
the transaction snapshot *is* a consideration.

> Anyway, any suggestion that randomly breaks user applications is not
> good. If there is a good reason to do that, OK, but I don't see that
> here. 

The good reason is adding functionality.  Or is it your position that
the functionality under discussion is not worth any syntax breakage,
no matter how narrowly circumscribed?  If we take that position then
we can drop this whole thread, because nothing's going to happen.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Database file copy
Next
From: Marti Raudsepp
Date:
Subject: Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.