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

Started by Tom Lanealmost 23 years ago3 messagescomitters

tgl@sss.pgh.pa.us

almost 23 years ago

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...)

Christopher Kings-Lynne

chriskl@familyhealth.com.au

almost 23 years ago

In reply to: Tom Lane (#1)

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

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 ...

Show quoted text

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

Bruce Momjian

bruce@momjian.us

almost 23 years ago

In reply to: Tom Lane (#1)

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

Tom Lane wrote:

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...)

TODO updated:

* -Have standalone backend read postgresql.conf (Tom)

I hadn't realized initdb shared_buffers would be effected by this, but
it makes sense it would.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073