Re: [COMMITTERS] pgsql: Background worker processes

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Background worker processes
Date: 2012-12-06 21:35:38
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera wrote:
> Background worker processes

I had tested this on EXEC_BACKEND some time ago, and it worked fine, but
I had neglected since then, and now I find it fails with a pretty
strange message on startup. Also, Andres and I have been talking about
other possible problems in that scenario (mostly that the order in which
shared libraries are loaded might not be deterministic, and this would
cause the whole approach to fall down).

I'm considering reverting this; but since it won't cause a visible
problem unless and until a worker is loaded, leaving it in place might
enable someone else to peek at it while I come up with some idea to
handle the broken EXEC_BACKEND case ...

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-12-07 04:10:08 pgsql: Improve pl/pgsql to support composite-type expressions in RETURN
Previous Message Alvaro Herrera 2012-12-06 21:02:11 pgsql: Background worker processes

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-12-06 22:01:16 Re: why can't plpgsql return a row-expression?
Previous Message Jeff Davis 2012-12-06 21:31:22 Re: Commits 8de72b and 5457a1 (COPY FREEZE)