From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | darrenk(at)insightdist(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Disk block size issues. |
Date: | 1998-01-09 18:36:15 |
Message-ID: | 199801091836.NAA01174@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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?
I like that, but the postmaster and each backend would have to read that
file before starting, or the postmaster can pass it down into the
postgres backend via a command-line option.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-09 20:10:11 | Re: [HACKERS] column labels now with obligatory 'as' |
Previous Message | Keith Parks | 1998-01-09 18:30:59 | Re: Trouble with exp() on S/Linux? |