Re: pgsql-server/src/backend bootstrap/bootstrap.c ... - Mailing list pgsql-committers

From Christopher Kings-Lynne
Subject Re: pgsql-server/src/backend bootstrap/bootstrap.c ...
Date
Msg-id 05f101c371c4$2079fca0$2800a8c0@mars
Whole thread Raw
In response to pgsql-server/src/backend bootstrap/bootstrap.c ...  (tgl@svr1.postgresql.org (Tom Lane))
List pgsql-committers
Cool.  That fixes the problem I was having perfectly.

Chris

----- Original Message -----
From: "Tom Lane" <tgl@svr1.postgresql.org>
To: <pgsql-committers@postgresql.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@svr1.postgresql.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
>


pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server/src/backend/access/nbtree nbtinsert.c
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server/src/backend/utils/adt formatting.c