Re: postgres block_size problem
От | Peter Eisentraut |
---|---|
Тема | Re: postgres block_size problem |
Дата | |
Msg-id | 495A285F.5080000@gmx.net обсуждение исходный текст |
Ответ на | postgres block_size problem ("Bhujbal, Santosh" <sbhujbal@starentnetworks.com>) |
Список | 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.
В списке pgsql-admin по дате отправления: