Philip Warner <[EMAIL PROTECTED]> writes: >> Considering that the data we are working with is binary, and may contain >> nulls, any code that insisted on null-termination would probably be ipso >> facto broken. > But we're not; this is the same code that sends the COPY output back to PG. Oh, isn't this the code that pushes large-object bodies around? I should think the problem would've been noticed much sooner if not... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
- [HACKERS] beta6 pg_restore core dumps Tatsuo Ishii
- Re: [HACKERS] beta6 pg_restore core dumps Tom Lane
- Re: [HACKERS] beta6 pg_restore core dumps Tom Lane
- Re: [HACKERS] beta6 pg_restore core dumps Tatsuo Ishii
- Re: [HACKERS] beta6 pg_restore core dumps Philip Warner
- Re: [HACKERS] beta6 pg_restore core dumps Tom Lane
- Re: [HACKERS] beta6 pg_restore core d... Philip Warner
- Re: [HACKERS] beta6 pg_restore co... Tom Lane
- Re: [HACKERS] beta6 pg_restor... Philip Warner
- Re: [HACKERS] beta6 pg_restor... Tom Lane
- Re: [HACKERS] beta6 pg_restor... Philip Warner
- Re: [HACKERS] beta6 pg_restor... Tom Lane
- Re: [HACKERS] beta6 pg_restor... Philip Warner
- Re: [HACKERS] beta6 pg_restore core dumps Martin Renters