Andrew Dunstan <and...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
