Re: [HACKERS] Variable Block Size Dilemma - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Variable Block Size Dilemma
Date
Msg-id 199801252021.PAA24397@candle.pha.pa.us
Whole thread Raw
In response to Variable Block Size Dilemma  (darrenk@insightdist.com (Darren King))
List pgsql-hackers
>
>
> I'm stuck as to how to make this a parameter for the backend.
>
> The postmaster could read a pg_blocksize file and then pass that,
> but how could _that_ be set differently when calling the same
> copy of initdb?
>
> I'd like to avoid having to set it in the Makefile in the way
> that the NAMEDATALEN and OIDNAMELEN variables are set up.
>
> *small lightbulb on*
>
> Would it be acceptable for this to be in a file in the PGLIB
> directory?  This could be read in by initdb and then passed along
> to the postgres calls.  Does this seem reasonable and/or clean?
>
> Or is there a really obvious way that I'm just not seeing right now?

You ask about the block size as part of initdb, and create a file in
/pgsql/data as part of initdb's work.  Then each postmaster reads the
file, and passes the value to each backend as a parameter.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: darrenk@insightdist.com (Darren King)
Date:
Subject: Variable Block Size Dilemma
Next
From: Brett McCormick
Date:
Subject: Re: [HACKERS] array questions still stands