Re: fork/exec patch

From: Neil Conway <neilc(at)samurai(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, "'pgsql-patches(at)postgresql(dot)org'" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: fork/exec patch
Date: 2003-12-14 21:41:16
Message-ID: 87y8tf9iwz.fsf@mailbox.samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-hackers-win32 pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I don't think we ever discussed it, but it seemed logical and a minimal
> change to the code. We already have a GUC write of non-default values
> for exec and no one had issues with that.

For the record, I think that is ugly as well :-)

Anyway, I'm not necessarily arguing that using shmem is the right way
to go here -- that was merely an off-the-cuff suggestion. I'm just
saying that whatever solution we end up with, ISTM we can do better
than writing out + reading in a file for /every/ new connection.

-Neil

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-12-14 21:56:42 Re: [PATCHES] fork/exec patch
Previous Message Bruce Momjian 2003-12-14 21:29:48 Re: fork/exec patch

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Bruce Momjian 2003-12-14 21:56:42 Re: [PATCHES] fork/exec patch
Previous Message Bruce Momjian 2003-12-14 21:29:48 Re: fork/exec patch

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-12-14 21:56:42 Re: [PATCHES] fork/exec patch
Previous Message Bruce Momjian 2003-12-14 21:29:48 Re: fork/exec patch