On Mon, Jan 16, 2006 at 11:57:35AM +0100, Francesco Formenti - TVBLOB S.r.l.
wrote:
> Jim C. Nasby wrote:
>
> >On Thu, Jan 12, 2006 at 06:11:32PM +0100, Francesco Formenti - TVBLOB
> >S.r.l. wrote:
> >
> >
> >>I put an ACCESS EXCLUSIVE LOCK on the table of objects at the beginning
> >>of the s
On Fri, Dec 02, 2005 at 10:15:04AM -0500, Tom Lane wrote:
> "Francesco Formenti - TVBLOB S.r.l." <[EMAIL PROTECTED]> writes:
> > I have a problem about deadlock. I have several stored procedures; only
> > one of them uses ACCESS EXCLUSIVE LOCK on a table; however, all the
> > stored procedures ca
"Francesco Formenti - TVBLOB S.r.l." <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Probably you have been careless about avoiding "lock upgrade"
>> situations.
> Unfortunately, the first operation I do after the "BEGIN" declaration is
> the LOCK TABLE in access exclusive mode, and is the only
Tom Lane wrote:
"Francesco Formenti - TVBLOB S.r.l." <[EMAIL PROTECTED]> writes:
I have a problem about deadlock. I have several stored procedures; only
one of them uses ACCESS EXCLUSIVE LOCK on a table; however, all the
stored procedures can access to that table, using SELECT, INSERT or UP
"Francesco Formenti - TVBLOB S.r.l." <[EMAIL PROTECTED]> writes:
> I have a problem about deadlock. I have several stored procedures; only
> one of them uses ACCESS EXCLUSIVE LOCK on a table; however, all the
> stored procedures can access to that table, using SELECT, INSERT or UPDATE.
> The stor
Hi all,
I have a problem about deadlock. I have several stored procedures; only
one of them uses ACCESS EXCLUSIVE LOCK on a table; however, all the
stored procedures can access to that table, using SELECT, INSERT or UPDATE.
The stored procedures are called by different processes of an external
