From: | Integration <abrams(at)philos(dot)umass(dot)edu> |
---|---|
To: | hackers(at)postgresql(dot)org |
Subject: | My 2c on adjustable blocksizes |
Date: | 1998-01-06 04:08:10 |
Message-ID: | 199801060408.XAA32273@lessing.oit.umass.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I would like to stand up as being very much in favor of two related things:
(1) adjustable blocksizes
(2) a larger MAX TUPLE size
As far as I can tell (and that ain't far), there would only be relatively
minor changes that would have to be made to give the option of allowing
the user to select 2, 4, 8 or 16 as the blocksize. Concurrently, it
would seem wise to simply up the max tuple size to 32k. It seems to me
unlikely that this would have a noticeable performance impact. In order
to do this, we would need to know about the 32 bit ItemIdData structure in
/storage/itemid.h (see my previous posts). It was recommended to me that
lp_flags might still be only using 2 of the 6 bits allocated to it. If
so, increasing lp_offset to 15 and lp_len to 15, i.e. 2^15 bits, i.e.
32768 bytes max tuple size, would be possible! I think!
Just my 2 cents.
Eddie
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-01-06 04:36:06 | Re: [HACKERS] Postgres acl |
Previous Message | Kevin Witten | 1998-01-06 04:05:30 | Postgres acl |