RE: Hardwired MAXBACKENDS limit could be history

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: Hardwired MAXBACKENDS limit could be history
Date: 2001-01-26 17:29:08
Message-ID: 8F4C99C66D04D4118F580090272A7A234D32C0@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I'm not thinking about getting this done in time for 7.1, but I think
> it'd be a nice cleanup for 7.2.
>
> Bruce, a TODO item please:
> * Remove compile-time upper limit on number of backends
> (MAXBACKENDS)

Did you ever consider remove per-backend semaphores at all?
We use them to sleep waiting for lock (ie when someone awake
us by changing our semaphore) - why don't use sigpause and
some signal? Semaphores are good to sync access to *shared*
resources but it's not that case here.

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2001-01-26 17:30:05 Re: Open 7.1 items
Previous Message Mikheev, Vadim 2001-01-26 17:07:40 RE: Permissions on CHECKPOINT