Re: pg_restore silently chokes on object comments/descriptions ending in a backslash - Mailing list pgsql-bugs

From Julian Mehnle
Subject Re: pg_restore silently chokes on object comments/descriptions ending in a backslash
Date
Msg-id 201107271728.25202.julian@mehnle.net
Whole thread Raw
In response to Re: pg_restore silently chokes on object comments/descriptions ending in a backslash  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_restore silently chokes on object comments/descriptions ending in a backslash
List pgsql-bugs
Tom Lane wrote:

> Julian Mehnle <julian@mehnle.net> writes:
> > I'm subscribed to the pgsql-bugs list, so no need to CC me. :-)
>
> cc to people in the thread is the established practice on these lists.
> It provides a bit more robustness when the lists are busy or slow.

Got it.  I'll try to remember that and CC others when posting, and will=20
also not take offense when receiving extra CCs.

> > What would "removing that code entirely" mean?
>
> I was wondering why it's necessary to parse the entry in the dump file
> at all, rather than just spit it out to PQexec as-is.  There's probably
> a reason, but maybe we can find another way to solve whatever the
> real problem is.

I see.  Given that I'm only a Pg user, not a Pg developer, I have no=20
opinion on this.  Thanks for the explanation, though!

-Julian

pgsql-bugs by date:

Previous
From: "Nivas"
Date:
Subject: BUG #6132: Cannot install rpm files
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_restore silently chokes on object comments/descriptions ending in a backslash