From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How are locks managed in PG? |
Date: | 2008-12-22 02:42:58 |
Message-ID: | 20081222024258.GE4200@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Dec 21, 2008 at 08:46:15PM -0500, Jonah H. Harris wrote:
> On Fri, Dec 19, 2008 at 7:49 AM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> >> Oracle on the other hand stores the lock information directly in
> >> the data block that is locked, thus the number of locks does not
> >> affect system performance (in terms of managing them).
> >>
> >> I couldn't find any description on which strategy PG applies.
> >
> > None of the above. We're smarter than everyone else.
>
> Which is why Oracle's locks are more scalable than PG's?
You've been talking about your super-secret test which you allege,
quite implausibly, I might add, to have Oracle (8i, even!) blowing
PostgreSQL's doors off for weeks now.
Put up, or shut up.
Regards,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2008-12-22 03:48:18 | Re: How are locks managed in PG? |
Previous Message | Jonah H. Harris | 2008-12-22 01:46:15 | Re: How are locks managed in PG? |