Re: advisory locks and permissions - Mailing list pgsql-hackers

From Kevin Brown
Subject Re: advisory locks and permissions
Date
Msg-id 20060921234446.GH11514@filer
Whole thread Raw
In response to Re: advisory locks and permissions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Doesn't creating many temp tables in a transaction do the same thing?
> 
> True, but it's a tad harder/less likely that you'd accidentally cause
> a problem that way.

Then why not use a GUC (that only an administrator can set) to control
the maximum number of advisory locks a given backend can take at any
one time?  Then it becomes the DBA's problem (and solution) if someone
manages to run the database out of shared memory through this
mechanism.



-- 
Kevin Brown                          kevin@sysexperts.com


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_upgrade: downgradebility
Next
From: Jeff Frost
Date:
Subject: Re: Cause of moving-target FSM space-needed reports