| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
| Cc: | Ken Mort <kenmort(at)mort(dot)port(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] 8K block limit |
| Date: | 1999-02-17 13:59:04 |
| Message-ID: | 199902171359.WAA01937@ext16.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Mon, 15 Feb 1999, Ken Mort wrote:
>
> > Already asked this in the other lists so here.
> >
> > I need to store some polygons that are larger than 8K.
> > I was reading in hackers archives talk about a solution
> > to the 8K limit. Was anything done? If so, what do I
> > need to do to solve my problem?
>
> There is an option that can be set at compile time to set the block size
> from 8k to something like 32 or 64K (not sure which).
I think it is 32k. (tuple offset in a block is limited to 15 bits)
> Note: Changing the block size may have a performance hit however.
Why?
---
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Horak Daniel | 1999-02-17 14:19:25 | interface between backend and dynamicly loaded modules |
| Previous Message | jose' soares | 1999-02-17 12:00:50 | varchar function |