From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Do we need a ShmList implementation? |
Date: | 2010-09-20 16:44:26 |
Message-ID: | 1285001066.1733.5777.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2010-09-20 at 12:35 -0400, Tom Lane wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> > Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> >> My understanding is that we used to have that and it was removed
> >> for the reasons Heikki states. There are still vestigial bits
> >> still in code.
>
> There's nothing vestigial about SHM_QUEUE --- it's used by the lock
> manager.
Yes, I was talking about an implementation that allocated memory as
well. There are sections of IFDEF'd out code there...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-09-20 16:47:06 | Re: Do we need a ShmList implementation? |
Previous Message | Andrew Dunstan | 2010-09-20 16:42:28 | Re: compile/install of git |