Re: fork/exec

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fork/exec
Date: 2004-02-02 01:11:34
Message-ID: 26218.1075684294@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> writes:
> Nice. Could perhaps also get it to do the ugly and oft repeated
> setitimer(ITIMER_PROF, &prof_itimer, NULL) and beos_backend_startup() bits,
> which currently contribute greatly in making the post-fork code unclear.

Good point.

> Flip you for it? :-)

Go for it, I've got plenty on my plate already ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-02-02 01:23:46 Re: Idea about better configuration options for sort memory
Previous Message Tom Lane 2004-02-02 01:06:54 Re: Q: How ORDER BY is being done inetrnally?