From: Doug McNaught <doug@mcnaught.org>
To: pilsl@goldfisch.at
Cc: pgsql-general@postgresql.org
Subject: Re: 7.2.3: tuple is too big (max 8136)
Date: 01 Nov 2002 08:50:54 -0500
Message-ID: <m37kfx9z5t.fsf@varsoon.wireboard.com> (raw)
References: <20021101143348.A7426@goldfisch.at>
pilsl@goldfisch.at writes:
> I got this error on older versions and was told to
> upgrade. Unfortunately I run into the very same error with 7.2.3.
>
> I have a table with 1600 cols (for testing) and insert one row into
> it which results in this error:
It's possible you are hitting the maximum column limit rather than the
tuple size limit. The FAQ list the max columns in a table as:
"250-1600 depending on column types"
So try a tuple of the same size but fewer columns and see if that's
the issue.
> I searched my whole systems for old libraries from a previous version
> but I'm quite sure that my upgrade was quite a clean and successful
> one...
I'm sure you're right but it's always good to double-check. ;)
-Doug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: doug@mcnaught.org, pilsl@goldfisch.at, pgsql-general@postgresql.org
Subject: Re: 7.2.3: tuple is too big (max 8136)
In-Reply-To: <m37kfx9z5t.fsf@varsoon.wireboard.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox