| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Debugging deadlocks |
| Date: | 2005-04-02 05:50:54 |
| Message-ID: | 87r7htsp4x.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> > On Fri, Apr 01, 2005 at 10:14:07PM -0500, Paul Tillotson wrote:
> >> ...
>
> > Well, at that point you need to take a lock in order to be able to
> > manage locks. Managing not to step on your own feet in that scenario
> > is complex, to say the least, if not downright impossible.
>
> 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. In that case there's a fixed amount of space per page reserved in
advance for storing locks.
Actually I think it's a bit more complicated. But that's the idea.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-02 06:09:25 | Re: [HACKERS] plPHP in core? |
| Previous Message | Peter Eisentraut | 2005-04-02 05:41:04 | Re: [HACKERS] plPHP in core? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-02 06:09:25 | Re: [HACKERS] plPHP in core? |
| Previous Message | Peter Eisentraut | 2005-04-02 05:41:04 | Re: [HACKERS] plPHP in core? |