Thread

1. Variable Block Size Dilemma

   Darren King <darrenk@insightdist.com> — 1998-01-25T19:38:58Z

   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?
   
   darrenk
   
   

2. Re: [HACKERS] Variable Block Size Dilemma

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-01-25T20:21:39Z

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