Skip site navigation (1) Skip section navigation (2)

Re: Hardwired MAXBACKENDS limit could be history

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Hardwired MAXBACKENDS limit could be history
Date: 2001-01-26 17:47:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> 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?

That'll fail if the signal arrives before the sigpause(), no?

> Semaphores are good to sync access to *shared*
> resources but it's not that case here.

The thing we really need here is that the right thing has to happen
if the V() occurs before our P(), ie, the V() has to be remembered
so that we will fall through the P() without blocking.

What I'd like to look at sometime soon is using POSIX semaphores
instead of SysV semaphores.  But we need stateful semaphores,
not signals.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Zeugswetter Andreas SBDate: 2001-01-26 17:52:33
Subject: AW: Open 7.1 items
Previous:From: Tibor LaszloDate: 2001-01-26 17:30:38
Subject: Re: serial values and odbc

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group