> The currently-checked-in sources are not working very well for me.
> In particular, I can't restore from my pg_dump because COPY IN
> coredumps; and a little experimentation shows that COPY OUT does too.
> 
> Is anyone else seeing this?
> 
> The immediate cause of the dumps seems to be trying to free() a pointer
> value 0x1.  I suspect it's got something to do with the two-to-four-byte
> atttypmod changeover, but can't prove that.
> 
> template1=> \copy pg_shadow to -
> QUERY: COPY pg_shadow TO stdout
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or while processing the request.
> We have lost the connection to the backend, so further processing is impossible.
>   Terminating.

Thanks.  Should be fixed now.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

In response to

• Current sources dump core on COPY IN/OUT at 1998-07-15 18:41:26 from Tom Lane

pgsql-hackers by date

Next:	From: Hannu Krosing	Date: 1998-07-15 19:52:25
	Subject: Re: [INTERFACES] Re: [HACKERS] changes in 6.4
Previous:	From: Tom Lane	Date: 1998-07-15 18:41:26
	Subject: Current sources dump core on COPY IN/OUT