Skip site navigation (1) Skip section navigation (2)

Re: Debugging deadlocks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Debugging deadlocks
Date: 2005-04-02 06:21:21
Message-ID: 1642.1112422881@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> I looked at Paul's first message and thought "nah, that won't work
>> because ... because ... hmm ... hmmm ..."

> For what it's worth, this would be very similar to how Oracle handles such
> locks.

[ slightly alarmed ]  Do they have a patent on the way they do it?

> In that case there's a fixed amount of space per page reserved in
> advance for storing locks.

Paul's idea involved using a variable amount of space (ie, whatever's
free) ... which might be sufficient to escape whatever hypothetical
patent Oracle or someone else might hypothetically have on this idea.
Or not.  Pardon me for feeling a bit skittish at the moment.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-04-02 06:31:13
Subject: Re: [HACKERS] plPHP in core?
Previous:From: Marc G. FournierDate: 2005-04-02 06:19:16
Subject: Re: [HACKERS] plPHP in core?

pgsql-general by date

Next:From: Tom LaneDate: 2005-04-02 06:31:13
Subject: Re: [HACKERS] plPHP in core?
Previous:From: Marc G. FournierDate: 2005-04-02 06:19:16
Subject: Re: [HACKERS] plPHP in core?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group