Re: LOCK DATABASE - Mailing list pgsql-general

From Josh Kupershmidt
Subject Re: LOCK DATABASE
Date
Msg-id CAK3UJRGURH6-9AoeOPrgWroWwo5xSsSS40zNL7vPW0BZeQ+7KQ@mail.gmail.com
Whole thread Raw
In response to Re: LOCK DATABASE  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general
On Thu, Dec 15, 2011 at 2:01 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> On Thu, Dec 15, 2011 at 10:17 AM, Eliot Gable
> <egable+pgsql-general@gmail.com> wrote:
>> Is this bogus, or is it an upcoming feature?
>>
>> http://wiki.postgresql.org/wiki/Lock_database

LOCK DATABASE was brought up earlier this year:
  http://archives.postgresql.org/pgsql-hackers/2011-05/msg00886.php

which is about when that wiki page was created.

> The page says: "This functionality is not implemented in PostgreSQL,
> and is not planned to be yet"  So I'd gues it's an ansi SQL Spec
> command that is not implemented and just included for completeness.

I don't think anything like that is in the SQL standard; there is
almost nothing, at least in a SQL:2008 draft I looked through, about
explicit locking.

Josh

pgsql-general by date:

Previous
From: Andreas 'ads' Scherbaum
Date:
Subject: REMINDER: FOSDEM 2012 - PostgreSQL Devroom: Call for Speakers
Next
From: Filip Rembiałkowski
Date:
Subject: segfault with plproxy