The page size is only really the size of disk allocated each time. You
can get many rows into a page.
As you said you can't use LO's, perhaps the page size is your only
chance (although I'm not sure if the text/varchar types are hardcoded to
a max 4k anyhow.
Peter
--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
-----Original Message-----
From: Nelson Ferreira Junior [mailto:nelson@radix.com.br]
Sent: Monday, April 17, 2000 10:31 PM
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Large strings
Nelson Ferreira Junior wrote:
> Hi,
>
> I have a JDBC aplication that actualy works with Oracle and I am
> porting it PostgreSQL. The trouble is that I have some rows with type
> "LONG" (in Oracle) where are stored strings with up to 20Kb and
> PostgreSQL doesn't hava this type and seems to be impossible to store
> strings larger than 8Kb with the types "TEXT" or "VARCHAR".
> What can I do ?!?!
>
> thanks.
Now I read something about changing the BLOCK SIZE to a higher
value and recompiling the backend. But it will require more disk space
to
store the data, isn't it? How much disk space will I need if a chage
the
block size to 32K? Will it decrease performance or confiability ? Before you suggest me to use BLOBs to store
theselarge strings,
I'd say that I cannot change my aplication in that way.
Thanks
again.