Search Postgresql Archives

Re: Locking entire database

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/15/07, hubert depesz lubaczewski <depesz@xxxxxxxxxx> wrote:
> On Fri, Sep 14, 2007 at 04:48:08PM +0300, Panagiotis Pediaditis wrote:
> > Is there some way of locking all database tables in a transaction
> > without knowing their names
> > or even better just locking the entire database? I know this is bad
> > tactics but there is a specific
> > case where i need it. Can it be done?
>
> there is no such thing, but you can use "advisory locks" to this
> purpose.

that would require taking a shared advisory lock for every
transaction...pretty big price to pay imo, but it would work.  I
thought about it for a bit and I don't know if there is any other way
to do it.

merlin

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux