Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Variable Block Size Dilemma

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: darrenk(at)insightdist(dot)com (Darren King)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Variable Block Size Dilemma
Date: 1998-01-25 20:21:39
Message-ID: 199801252021.PAA24397@candle.pha.pa.us (view raw or flat)
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us

In response to

pgsql-hackers by date

Next:From: Brett McCormickDate: 1998-01-25 23:33:03
Subject: Re: [HACKERS] array questions still stands
Previous:From: Bruce MomjianDate: 1998-01-25 19:53:21
Subject: Re: [HACKERS] Group By, NULL values and inconsistent behaviour.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group