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-04 23:59:17
Message-ID: 4F04E7D5.2080207@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:
> 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? Or can we just issue a SET to make it what it
needs to be?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gianni Ciolli 2012-01-04 23:59:47 Re: Autonomous subtransactions
Previous Message Samuel PHAN 2012-01-04 23:58:19 Re: Add SPI results constants available for PL/*