From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Julian Mehnle <julian(at)mehnle(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_restore silently chokes on object comments/descriptions ending in a backslash |
Date: | 2011-07-27 14:35:19 |
Message-ID: | 7994.1311777319@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
You can set your subscription so the listserv won't send you an extra
copy, I believe, but I don't know the incantation offhand.
> Tom Lane wrote:
>> Not sure about a simple fix,
>> and I rather wonder if we shouldn't try to remove that code entirely
>> instead of "fix" it.
> 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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nivas | 2011-07-27 15:19:15 | BUG #6132: Cannot install rpm files |
Previous Message | Julian Mehnle | 2011-07-27 04:01:57 | Re: pg_restore silently chokes on object comments/descriptions ending in a backslash |