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

From Florian Pflug
Subject Re: LOCK for non-tables
Date
Msg-id 9E3F151F-8FFA-4557-8473-71F55CBE47F8@phlo.org
Whole thread Raw
In response to Re: LOCK for non-tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: LOCK for non-tables  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Jan15, 2011, at 02:03 , Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Me, too.  But I don't agree with your particular choice of small
>> syntax adjustment.  Maybe we should just let the issue drop for now.
>> Nobody's actually complained about this that I can recall; it's just a
>> comment that's been sitting there in pg_dump for ages, and I was
>> inspired to think of it again because of the SQL/MED work.  I'm not
>> sufficiently in love with this idea to walk through fire for it.
> 
> Agreed.  Once there's some pressing need for it, it'll be easier to make
> the case that some amount of incompatibility is acceptable.

Assuming that day will come eventually, should we deprecate the LOCK <table>
shortcut now to ease the transition later? If people want that, I could go
through the docs and add some appropriate warnings.

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Recovery control functions
Next
From: Simon Riggs
Date:
Subject: Re: Recovery control functions