Re: advisory locks and permissions

From: Kevin Brown <kevin(at)sysexperts(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: advisory locks and permissions
Date: 2006-09-21 23:44:46
Message-ID: 20060921234446.GH11514@filer
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)sysexperts(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Frost 2006-09-22 00:31:28 Re: Cause of moving-target FSM space-needed reports
Previous Message Alvaro Herrera 2006-09-21 22:12:22 Re: pg_upgrade: downgradebility