We were getting the following error on executing a COPY command on
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
What could be the possible solution to this?
This email and any attachments may contain legally privileged and/or confidential information of Starent Networks, Corp. and is intended only for the individual or entity named in the message. The information transmitted may not be used to create or change any contractual obligations of Starent Networks, Corp. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this e-mail and its attachments by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify the sender immediately -- by replying to this message or by sending an email to postmaster(at)starentnetworks(dot)com -- and destroy all copies of this message and any attachments without reading or disclosing their contents. Thank you.
pgsql-admin by date
|Next:||From: Laszlo Nagy||Date: 2008-12-30 13:17:01|
|Subject: Re: rebellious pg stats collector (reopened case)|
|Previous:||From: Iñigo Martinez Lasala||Date: 2008-12-30 11:02:36|
|Subject: Context-switch storm in 8.1.15|