Skip site navigation (1) Skip section navigation (2)

Re: postgres block_size problem

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Bhujbal, Santosh" <sbhujbal(at)starentnetworks(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: postgres block_size problem
Date: 2008-12-30 13:55:43
Message-ID: 495A285F.5080000@gmx.net (view raw or flat)
Thread:
Lists: pgsql-admin
Bhujbal, Santosh wrote:
> Hi All,
> 
> We were getting the following error on executing a COPY command on 
> postgres8.2.0.
> 
> SQL execution failed, Internal error. SQL Statement: (COPY command failed with error: ERROR:  row is too big: size 8200, maximum size 8136)
> 
> So, in order to fix the error we tried increasing the block size to 16k 
> and recompiled the postgres library. The problem at hand was resolved 
> with the new postgres library and we were now able to populate data for 
> the mentioned query successfully. However, this experiment fails when we 
> tried to run the new postgres on data directory generated with 8k block 
> size which is likely to occur during an upgrade with postgres log 
> showing the following error:
> 
>  
> 
> 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.
> 
>  
> 
> What could be the possible solution to this?

If you want to migrate data from an 8k block size data directory to a 
16k block size data directory, you need to do a dump and restore, just 
like on a major version upgrade.

In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-12-30 18:51:50
Subject: Re: postgres block_size problem
Previous:From: Laszlo NagyDate: 2008-12-30 13:17:01
Subject: Re: rebellious pg stats collector (reopened case)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group