| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
| 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-12 09:11:52 |
| Message-ID: | 199910120911.SAA02979@srapc451.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 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. For example:
>>
>> (1) there is a file called PG_BLKSZ under $PGDATA.
>>
>> (2) postmaster checks the contents of the file to see if it was
>> compiled in the same BLKSZ.
>>
>> (3) If not, give some error messages and exit.
>
>There is special file pg_control for the WAL purposes - good
>place for the BLCKSZ...
Nice. Do you have some functions to access the file? Seems it is a
binary file.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 1999-10-12 09:12:11 | Re: Scripts (was Re: [HACKERS] Re: [INTERFACES] Next release is |
| Previous Message | Vadim Mikheev | 1999-10-12 09:00:11 | Re: [HACKERS] Different BLKSZ |