Re: When malloc returns zero ...

From: Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: When malloc returns zero ...
Date: 2000-05-02 08:50:36
Message-ID: Pine.GSO.4.02A.10005021047051.13753-100000@Iller.DoCS.UU.SE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 1 May 2000, Tom Lane wrote:

> Er, what's wrong with elog(DEBUG)?

Well, it says "DEBUG", not "ERROR", that's all. I'm using this in fact but
it's suboptimal.

> Doesn't the postmaster need to reread the config file itself in order to
> be sure to pass the new values to subsequently-started backends?

Good that you mention that ... :)

> Or is your plan that newly started backends will always parse the
> config file for themselves? In that case I'm not clear on why you
> care about the postmaster environment at all.

So you can set buffers, max backends, and that sort of static stuff. I
think that each backend reading the config file on startup is
unnecessarily slow.

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message SAKAIDA 2000-05-02 09:17:13 Re: psql \l error
Previous Message Peter Eisentraut 2000-05-02 08:46:53 Re: shmem_seq may be a bad idea