From: | "Matt Friedman" <matt(at)daart(dot)ca> |
---|---|
To: | "Mitch Vincent" <mitch(at)venux(dot)net>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres limitation -what does it mean? (8k row limit) |
Date: | 2001-01-27 17:44:11 |
Message-ID: | 001b01c08888$c5154850$e8804318@mattq3h8budilr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the info on how to alter the BLCKSZ.
Sorry, but I'm still not 100 percent clear on what the limit effects. My
assumption is that all of the data within one tuple or row must not exceed a
size of 8k, provided that BLCKSZ is set to 8k.
However, this doesn't seem right to me. What specifically is the meaning of
the 8k limit?
Matt Friedman
Spry New Media
http://www.sprynewmedia.com
Lead Programmer/Partner
email: matt(at)sprynewmedia(dot)com
phone: 250 744 3655
fax: 250 370 0436
----- Original Message -----
From: "Mitch Vincent" <mitch(at)venux(dot)net>
To: "Matt Friedman" <matt(at)sprynewmedia(dot)com>; <pgsql-general(at)postgresql(dot)org>
Sent: Saturday, January 27, 2001 9:01 AM
Subject: Re: postgres limitation -what does it mean? (8k row limit)
> 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(at)daart(dot)ca>
> To: "Mitch Vincent" <mitch(at)venux(dot)net>; <pgsql-general(at)postgresql(dot)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(at)venux(dot)net>
> > To: <pgsql-general(at)postgresql(dot)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
> > >
> > >
> > >
> >
> >
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Karina | 2001-01-27 17:49:09 | Consulta. |
Previous Message | Jeff Duffy | 2001-01-27 17:06:59 | Re: JDBC connection failure |