Re: Tuple Max Size on 7.1 - Mailing list pgsql-general

From David Scholes
Subject Re: Tuple Max Size on 7.1
Date
Msg-id 3AF0C836.260AC560@cfourusa.com
Whole thread Raw
In response to Tuple Max Size on 7.1  (David Scholes <david@cfourusa.com>)
List pgsql-general
Sorry.  Perl drivers are Okay.  Our server was moved and pointing so I was
pointing to an old version.

After digging more into the CF problem it does appear to be the drivers.  I
changed the odbc.ini file to point to the new drivers that come with the
distribution but CF still seems to try and use the old version.  I renamed
the old libpgsqlodbc.so and then it quit working so it must have still been
using it.  CF bundles the odbc drivers with it's release so I guess I need
to move things around to get it working.  CF bundled unixODBC postgresql
drivers with their distribution.  But from what I've read the odbc drivers
from the pgsql 7.1 should also work.  Am I going to need to install the
unixODBC drivers instead?

Thanks, David

Tom Lane wrote:

> Doug McNaught <doug@wireboard.com> writes:
> > It's possible that the client drivers you're using weren't updated to
> > reflect the unlimited tuple size in 7.1.
>
> No; the error he's quoting is an internal backend failure, so it's
> not a client-side problem.  It looks to me like TOAST is failing to
> get the job done on compacting an oversize tuple, which is why I wanted
> to know more about the table in question.
>
>                         regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster


pgsql-general by date:

Previous
From: Sean Chittenden
Date:
Subject: Re: Ideal hardware configuration for pgsql
Next
From: Randall Perry
Date:
Subject: Perl Scope problem