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

Re: fork/exec patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>,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 23:53:22
Message-ID: 3694.1071446002@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32pgsql-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.

You can hardly claim that "no one had issues with that".  I complained
about it and I think other people did too.  It's a messy, ugly approach;
moreover we have no field experience that says it's reliable.

It may be the least messy, ugly approach available, but I concur with
Neil's wish to at least look for other answers.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-12-14 23:57:31
Subject: Re: [PATCHES] fork/exec patch
Previous:From: Tom LaneDate: 2003-12-14 23:45:01
Subject: Re: Walker/mutator prototype.

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2003-12-15 00:02:31
Subject: Re: fork/exec patch
Previous:From: Andrew DunstanDate: 2003-12-14 23:43:54
Subject: Re: [PATCHES] fork/exec patch

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2003-12-14 23:57:31
Subject: Re: [PATCHES] fork/exec patch
Previous:From: Andrew DunstanDate: 2003-12-14 23:43:54
Subject: Re: [PATCHES] fork/exec patch

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