Re: this is in plain text (row level locks)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: sailesh(at)cs(dot)berkeley(dot)edu
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)rbt(dot)ca>, Jenny - <nat_lazy(at)hotmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: this is in plain text (row level locks)
Date: 2003-07-24 22:14:44
Message-ID: 200307242214.h6OMEiu06003@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sailesh Krishnamurthy wrote:
> >>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> Tom> Sailesh Krishnamurthy <sailesh(at)cs(dot)berkeley(dot)edu> writes:
> >> Why not have the traditional approach of a lock table in shared
> >> memory, growing and shrinking as appropriate,
>
> Tom> Because we can't grow shared memory. Whatever size we get at
> Tom> startup is what we're stuck with. (I suppose we could try
> Tom> asking the kernel for additional segments, but there's every
> Tom> likelihood that that will fail.)
>
> We implemented a Shared Memory MemoryContext using OSSP libmm (used in
> Apache) for TelegraphCQ.
>
> If you think it's useful I can submit it as a patch.
>
> --
> Pip-pip
> Sailesh
> http://www.cs.berkeley.edu/~sailesh

^^^^^^^^^^^^^^^
Watch out, that code from Berkeley usually is a mess. :-)

Seriously, though, it would be good to see what you guys are up to.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-07-24 22:15:23 Re: this is in plain text (row level locks)
Previous Message Sailesh Krishnamurthy 2003-07-24 22:11:46 Re: this is in plain text (row level locks)