In your src/include directory of the PostgreSQL tree (pre 7.1 of course) --
edit config.h (after you run configure or config.h.in before) and look for
the line(s) :
/*
* Size of a disk block --- currently, this limits the size of a tuple.
* You can set it bigger if you need bigger tuples.
*/
/* currently must be <= 32k bjm */
#define BLCKSZ 32768
There I have mine to 32k, the upper limit.
Change it, save it, recompile PG, you will have to initdb and import all
your data too..
Viola!
Remember. Just because I haven't had any problems doesn't mena you won't.
Check the mailing list archives, I there was a thread on the possible
dangers of BLCKSZ.
Depending on what you're doing, you might want to check out 7.1 Beta (4 is
the latest I think), I've been running various beta versions for a month
(not in production) but it seems pretty stable and there is no limit on
tuple size :-)
-Mitch
----- Original Message -----
From: "Matt Friedman" <matt@daart.ca>
To: "Mitch Vincent" <mitch@venux.net>; <pgsql-general@postgresql.org>
Sent: Friday, January 26, 2001 11:32 PM
Subject: Re: postgres limitation -what does it mean? (8k row limit)
> I've been following this thread but it's not clear to me what an 8k row
> limit means exactly.
>
> Does it mean that the size of all the data in that row must not be greater
> than 8k? That seems very small to me.
>
> Also, how does one change BLCKSZ?
>
> Some more detail on the subject would be great. thank you.
>
> Matt Friedman
>
>
>
>
> ----- Original Message -----
> From: "Mitch Vincent" <mitch@venux.net>
> To: <pgsql-general@postgresql.org>
> Sent: Friday, January 26, 2001 7:28 PM
> Subject: Re: postgres limitation
>
>
> > > > the max size of a row...
> > >
> > > 8k in pre v7.1, no limit in v7.1 an dlater ...
> >
> > 32k really... BLCKSZ can be changed.. I've had no trouble running a
> > production database with BLCKSZ set to 32k though there might be issues
> I'm
> > not aware of..
> >
> > -Mitch
> >
> >
> >
>
>
