Re: pg_restore direct to database is broken for --insert dumps - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_restore direct to database is broken for --insert dumps
Date
Msg-id 1635.1325722525@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_restore direct to database is broken for --insert dumps  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 01/04/2012 06:20 PM, Tom Lane wrote:
>> But we'd have to deal with
>> standard-conforming strings some way.  The idea I had about that, since
>> we have an open database connection at hand, is to check the connected
>> backend's standard_conforming_strings state via PQparameterStatus.  If
>> it doesn't have the right setting then things are going to fail anyway.

> Do we care what it is?

Well, yeah, we care.

> Or can we just issue a SET to make it what it needs to be?

We already did, but I don't think the code in pg_backup_db has
convenient access to the value.  I might be wrong about that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gianni Ciolli
Date:
Subject: Re: Autonomous subtransactions
Next
From: Andrew Dunstan
Date:
Subject: Re: PL/Perl Does not Like vstrings