Re: pg_restore silently chokes on object comments/descriptions ending in a backslash

From: Julian Mehnle <julian(at)mehnle(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: pg_restore silently chokes on object comments/descriptions ending in a backslash
Date: 2011-07-27 17:28:21
Message-ID: 201107271728.25202.julian@mehnle.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:

> Julian Mehnle <julian(at)mehnle(dot)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
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
opinion on this. Thanks for the explanation, though!

-Julian

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2011-07-27 17:44:28 Re: pg_restore silently chokes on object comments/descriptions ending in a backslash
Previous Message Nivas 2011-07-27 15:19:15 BUG #6132: Cannot install rpm files