From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Different BLKSZ |
Date: | 1999-10-16 09:27:16 |
Message-ID: | 199910160927.SAA04947@ext16.sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > While doing some tests, I have encountered too many problems with
> > incompatible BLKSZ (the backend comipled in different BLKSZ with the
> > one in database). I know this is my fault, but it would be nice if
> > there is better way to avoid this kind of disaster.
>
> I think this is a fine idea, but BLKSZ is not the only critical
> parameter that should be verified at startup. RELSEG_SIZE is
> also critical and should be checked the same way. Are there any
> other configuration variables that affect database layout? I can't
> think of any offhand, but maybe someone else can.
I have committed changes for RELSEG_SIZE too. initdb required.
---
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Zakkr | 1999-10-16 13:01:02 | to_char(), md5() (long) |
Previous Message | Stéphane FILLON | 1999-10-16 06:30:56 | Tr: Functions documentations |