Re: pgsql-server/src/backend bootstrap/bootstrap.c ...

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: <pgsql-committers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)svr1(dot)postgresql(dot)org>
Subject: Re: pgsql-server/src/backend bootstrap/bootstrap.c ...
Date: 2003-09-03 02:36:04
Message-ID: 05f101c371c4$2079fca0$2800a8c0@mars
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Cool. That fixes the problem I was having perfectly.

Chris

----- Original Message -----
From: "Tom Lane" <tgl(at)svr1(dot)postgresql(dot)org>
To: <pgsql-committers(at)postgresql(dot)org>
Sent: Wednesday, September 03, 2003 3:04 AM
Subject: [COMMITTERS] pgsql-server/src/backend bootstrap/bootstrap.c ...

> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: tgl(at)svr1(dot)postgresql(dot)org 03/09/02 16:04:13
>
> Modified files:
> src/backend/bootstrap: bootstrap.c
> src/backend/tcop: postgres.c
>
> Log message:
> Cause standalone backend (including bootstrap case) to read the GUC
> config file if it exists. This was already discussed as being a good
> idea, and now seems the cleanest way to deal with initdb-time failures
> on machines with small SHMMAX. (The submitted patches instead modified
> initdb.sh to pass the correct sizing parameters, but that would still
> leave standalone backends prone to failure later. An admin who needs
> to use a standalone backend has enough trouble already, he shouldn't
> have to manually configure its shmem settings...)
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2003-09-03 14:59:48 pgsql-server/src/backend/utils/adt formatting.c
Previous Message Tom Lane 2003-09-02 22:10:17 pgsql-server/src/backend/access/nbtree nbtinsert.c