| From: | "Stupor Genius" <stuporg(at)erols(dot)com> |
|---|---|
| To: | "Pgsql-Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | <t-ishii(at)sra(dot)co(dot)jp> |
| Subject: | RE: [HACKERS] 8K block limit |
| Date: | 1999-02-18 10:50:52 |
| Message-ID: | 000001be5b2c$8d7b28a0$2898accf@darren |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Additional testings are welcome...
>
> >The max is 32k because of the aforementioned 15 bits available, but I'd
> >be a bit cautious of trying it. When I put this in, the highest I could
> >get to work on AIX was 16k. Pushing it up to 32k caused major breakage
> >in the system internals. Had to reboot the machine and fsck the file
> >system. Some files were linked incorrectly, other files
> disappeared, etc,
> >a real mess.
> >
> >Not sure exactly what it corrupted, but I'd try the 32k limit on a non-
> >production system first...
>
> I did above on 6.4.2. What kind of version are you using? Or maybe
> platform dependent problem?
My platform at the time was AIX 4.1.4.0 and it was an definitely AIX
that broke, not postgres.
Glad to hear it works at 32k on other systems though!
Darren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas IZ5 | 1999-02-18 11:06:38 | AW: [HACKERS] 8K block limit |
| Previous Message | Peter T Mount | 1999-02-18 07:18:02 | Re: [HACKERS] Continued problems with pgdump, Large Objects and crashing backends |