Re: postgres block_size problem

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: "Bhujbal, Santosh" <sbhujbal(at)starentnetworks(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres block_size problem
Date: 2009-01-01 06:20:06
Message-ID: 495C6096.2050106@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bhujbal, Santosh wrote:

> 2008-12-30 14:57:33 IST DETAIL: The database cluster was initialized
> with BLCKSZ 8192, but the server was compiled with BLCKSZ 16384.
>
> 2008-12-30 14:57:33 IST HINT: It looks like you need to recompile or
> initdb.

This error message tells you the answer. You can't run PostgreSQL with a
data directory that was initialized with a different block size. You
will need to dump and reload the database.

You really shouldn't be hitting the 8k row size limit anyway. PostgreSQL
uses out-of-line TOAST storage for large values, so the only way you're
likely to be hitting it is by having absurd numbers of small fields in
your tables (or maybe a custom data type for which you've not
implemented TOAST support?). If you have that many fields in your tables
it might be time to look at your schema design.

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Gerhard Heift 2009-01-01 13:41:08 How to cast a general record?
Previous Message Scott Marlowe 2009-01-01 05:09:50 Re: manage changes to views having depencies