Re: Extending to 32K row limit

Thanks Don. One more question: Does Postgres set aside an entire 8 K (or 32 K) of
hard disk space for the row; or, does it just use what's needed to store the
information? For example, if I only have one integer value in a row, does Postgres
set aside 8K of harddrive space or just sizeof(int) space (with some pointer where
other values in the row could be placed on the disk)?

I just wanted to make sure that my old data at 8 K wasn't going to take up 4 times as
much harddrive space after the 32K conversion.

Thanks.
-Tony




Don Baccus wrote:

> At 12:26 PM 8/8/00 -0500, Thomas Swan wrote:
> >>>>
>
>      At 12:24 PM 8/8/2000, G. Anthony Reina wrote:
>
>           I know that I've seen this answer before but can't seem to find it for
>           7.0.2 in the archives. Which file(s) need to be changed to have Postgres
>           default to 32K size row limits rather than 8K? Has anyone run into any
>           horror stories after going to 32K?
>
>      I've been running it for a while and fairly heavily without any problems...
>
> <<<<
>
> Folks using the OpenACS toolkit, which includes the AOLserver site run by
> AOL (did y'all know that's a Postgres site now? - just the AOLserver site,
> not all of AOL, don't get TOO excited) run with a 16KB blocksize if they
> follow our instructions.
>
> I've been running a couple of sites like that.
>
> Zero problems.
>
> - Don Baccus, Portland OR <dhogaza@pacifier.com>
> Nature photos, on-line guides, Pacific Northwest
> Rare Bird Alert Service and other goodies at
> http://donb.photo.net.

--
///////////////////////////////////////////////////
//   G. Anthony Reina, MD                       //
//   The Neurosciences Institute               //
//   10640 John Jay Hopkins Drive             //
//   San Diego, CA  92121                    //
//   Phone: (858) 626-2132                  //
//   FAX: (858) 626-2199                   //
////////////////////////////////////////////