Re: pg_restore direct to database is broken for --insert dumps

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: pg_restore direct to database is broken for --insert dumps
Date: 2012-01-05 14:51:07
Message-ID: 4F05B8DB.6030706@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/04/2012 06:20 PM, Tom Lane wrote:
>> Could we detect an appropriate line ending in ahwrite() after it's been
>> decompressed and buffer partial lines accordingly?
> Not easily: there could be newlines embedded in data strings or SQL
> identifiers.
>

Should we look at eliminating those newlines for the future by using
U&"" identifiers where there are embedded newlines and unicode escapes
for newlines in data strings?

Then at least we'd possibly be able to get rid of the kludge some time
in the future.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Benedikt Grundmann 2012-01-05 14:53:15 Re: Page Checksums + Double Writes
Previous Message Andrew Dunstan 2012-01-05 14:42:58 Re: PL/Perl Does not Like vstrings