Re: pg_restore (libpq? parser?) bug in 8 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_restore (libpq? parser?) bug in 8
Date
Msg-id 28195.1092318125@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_restore (libpq? parser?) bug in 8  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: pg_restore (libpq? parser?) bug in 8  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
"Andrew Dunstan" <andrew@dunslane.net> writes:
> I had a thought that might short-circuit this - do we even need pg_dump to
> use dollar quoting for non-text output, such as is required by pg_restore?

That's a possibility, but I'd rather work around it by finding a way for
pg_restore not to need to parse the dollar-quoted literal in the first
place.  I haven't heard a reason why it needs to parse the contents of a
CREATE FUNCTION entry.  If we guarantee not to put dollar-quoted
literals into the TOC types it *does* need to parse, ISTM we're good.
        regards, tom lane


pgsql-hackers by date:

Previous
From: LISTMAN
Date:
Subject: Re: [ADMIN] Where does the xlateSqlType symbol point
Next
From: Tom Lane
Date:
Subject: Re: Re: We have got a serious problem with pg_clog/WAL synchronization