Re: UPDATE: pg_dump fails due to invalid memory request - Mailing list pgsql-novice

From Michael Fuhr
Subject Re: UPDATE: pg_dump fails due to invalid memory request
Date
Msg-id 20050903200522.GA2255@winnie.fuhr.org
Whole thread Raw
In response to Re: UPDATE: pg_dump fails due to invalid memory request  (Michael Fuhr <mike@fuhr.org>)
List pgsql-novice
On Sat, Sep 03, 2005 at 10:52:44AM -0600, Michael Fuhr wrote:
> On Fri, Sep 02, 2005 at 08:48:34PM -0700, Morgan Kita wrote:
> > Obviously I will need to do more testing and try to debug,
> > but isn't it odd that I can select the data but not copy from it?
>
> That seems odd to me; maybe Tom or somebody else who knows PostgreSQL
> internals can explain why that might happen.

In tests I see different behavior between SELECT and COPY if the
type's output function doesn't call PG_DETOAST_DATUM on its argument:
SELECT returns the correct data but COPY doesn't.  Have you neglected
to call PG_DETOAST_DATUM?

--
Michael Fuhr

pgsql-novice by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: UPDATE: pg_dump fails due to invalid memory request
Next
From: "Morgan Kita"
Date:
Subject: Re: UPDATE: pg_dump fails due to invalid memory request