Re: [HACKERS] Disk block size issues. - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] Disk block size issues.
Date
Msg-id Pine.NEB.3.95.980109130826.16290K-100000@hub.org
Whole thread Raw
In response to Re: [HACKERS] Disk block size issues.  (darrenk@insightdist.com (Darren King))
Responses Re: [HACKERS] Disk block size issues.  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
On Fri, 9 Jan 1998, Darren King wrote:

> How about PG_BLOCK_SIZE?  Or if it's made a variable, DiskBlockSize, keeping
> it in the tradition of SortMem, ShowStats, etc.

    I know of one site that builds their Virtual Websites into
chroot()'d environments...something like this would be perfect for them,
as it would prvent them having to recompile for each individual size...

    But...initdb would have to have an appropriate option...and we'd
have to have a mechanism in place that checks that -k parameter is
actually appropriate.

    Would it not make a little more sense to have a pg_block_size file
created in the data directory that postmaster reads at startup?



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] column labels now with obligatory 'as'
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] varchar/char size