On Sun, Feb 04, 2007 at 23:43:48 -0800,
David Fetter <[EMAIL PROTECTED]> wrote:
> On Sun, Feb 04, 2007 at 03:18:07PM -0200, Jorge Godoy wrote:
> > Tom Lane <[EMAIL PROTECTED]> writes:
> >
> > > Jorge Godoy <[EMAIL PROTECTED]> writes:
> > >> I'm using PostgreSQL 8.1.4 and psql 8.1.4 as well.
> >
On Sun, Feb 04, 2007 at 03:18:07PM -0200, Jorge Godoy wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > Jorge Godoy <[EMAIL PROTECTED]> writes:
> >> I'm using PostgreSQL 8.1.4 and psql 8.1.4 as well.
> >
> > This was fixed in 8.1.5 ... or at least the only known cause was
> > fixed.
>
> Thanks
Tom Lane <[EMAIL PROTECTED]> writes:
> Jorge Godoy <[EMAIL PROTECTED]> writes:
>> I'm using PostgreSQL 8.1.4 and psql 8.1.4 as well.
>
> This was fixed in 8.1.5 ... or at least the only known cause was fixed.
Thanks! I'll bug OpenSuSE guys to release an 8.1.5 package ;-)
--
Jorge Godoy <
Jorge Godoy <[EMAIL PROTECTED]> writes:
> I'm using PostgreSQL 8.1.4 and psql 8.1.4 as well.
This was fixed in 8.1.5 ... or at least the only known cause was fixed.
2006-10-06 14:23 tgl
* src/: backend/utils/cache/catcache.c,
backend/utils/cache/syscache.c, include/utils/catcac
Hi!
There was a discussion with this same subject last week that seemed to be
caused by dump/restore with a wrong phpPgAdmin version.
I'm seeing the same error message for a development database where I always
use psql directly to make the maintenance and I had no dump/restore before it
started