| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Morgan Kita <mkita(at)verseon(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: UPDATE: pg_dump fails due to invalid memory request |
| Date: | 2005-09-03 20:05:23 |
| Message-ID: | 20050903200522.GA2255@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Morgan Kita | 2005-09-03 20:48:49 | Re: UPDATE: pg_dump fails due to invalid memory request |
| Previous Message | Michael Fuhr | 2005-09-03 19:01:34 | Re: UPDATE: pg_dump fails due to invalid memory request |