Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41195=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1UmVdA-0001ko-A5
 for pgsql-admin@arkaria.postgresql.org; Tue, 11 Jun 2013 20:57:28 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
 <pgsql-admin-owner+M41195=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1UmVd9-0004WE-N9
 for pgsql-admin@arkaria.postgresql.org; Tue, 11 Jun 2013 20:57:27 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.72)
 (envelope-from <alejandrob@pasteleros.org.ar>) id 1UmVd8-0004W9-Ve
 for pgsql-admin@postgresql.org; Tue, 11 Jun 2013 20:57:27 +0000
Received: from mail.pasteleros.org.ar ([200.49.144.54])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <alejandrob@pasteleros.org.ar>) id 1UmVd4-0000Up-CI
 for pgsql-admin@postgresql.org; Tue, 11 Jun 2013 20:57:26 +0000
Received: from mail.pasteleros.org.ar (unknown [127.0.0.1])
 by mail.pasteleros.org.ar (Postfix) with ESMTP id 4FDE02298E
 for <pgsql-admin@postgresql.org>; Tue, 11 Jun 2013 18:29:47 -0300 (ART)
X-Virus-Scanned: amavisd-new at pasteleros.org.ar
Received: from mail.pasteleros.org.ar ([127.0.0.1])
 by mail.pasteleros.org.ar (mail.pasteleros.org.ar [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id KoeybU40E3ej for <pgsql-admin@postgresql.org>;
 Tue, 11 Jun 2013 18:29:42 -0300 (ART)
Received: from [192.169.100.54] (unknown [192.169.100.54])
 by mail.pasteleros.org.ar (Postfix) with ESMTP id 948BD229C9
 for <pgsql-admin@postgresql.org>; Tue, 11 Jun 2013 18:29:42 -0300 (ART)
Message-ID: <51B78F2B.4060107@pasteleros.org.ar>
Date: Tue, 11 Jun 2013 17:57:15 -0300
From: Alejandro Brust <alejandrob@pasteleros.org.ar>
Reply-To: alejandrob@pasteleros.org.ar
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130503 Thunderbird/17.0.5
MIME-Version: 1.0
To: posgres support <pgsql-admin@postgresql.org>
Subject: postgres 9.2  error whit apostrophes
Content-Type: multipart/alternative;
 boundary="------------030103080805040101000202"
X-Pg-Spam-Score: -2.1 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.
--------------030103080805040101000202
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello, excuse my English first

we recently move from pg9.0 to pg 9.2 whit this method:

from a new server PG9.2 we did:
pg_dump -h server -p 5432 -U user -Fc -i -b base-name > bk.backup

after that in the new server
createdb -T template0 -E LATIN1 basename
pg_restore -h server -p 5432 -U user -d basename bk.backup

now we are having problems with updates on tables  whit apostrophes
like  >> o'higgins << on any character fields
First question:
            is there  any configurable parameter for PG9.2 that make 
            update tu02t00 set tu02pfusua = 'D'AGOSTINO'  work...
            the server error said   

ERROR: syntax error at or near "AGOSTINO" at character 187

Second question:
If there is no way to configure PG9.2 to accept this Cain of update
which is the best method to do a downgrade from 9.2 to 9.0 (we are not using any new function)


thanks in advance is ok?




--------------030103080805040101000202
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello, excuse my English first<br>
    <br>
    we recently move from pg9.0 to pg 9.2 whit this method:<br>
    <br>
    from a new server PG9.2 we did:<br>
    pg_dump -h server -p 5432 -U user -Fc -i -b base-name &gt; bk.backup<br>
    <br>
    after that in the new server<br>
    createdb -T template0 -E LATIN1 basename<br>
    pg_restore -h server -p 5432 -U user -d basename bk.backup<br>
    <br>
    now we are having problems with updates on tables&nbsp; whit apostrophes
    like&nbsp; &gt;&gt; o'higgins &lt;&lt; on any character fields<br>
    First question:<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; is there&nbsp; any configurable parameter for PG9.2 that
    make&nbsp; <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; update tu02t00 set tu02pfusua = 'D'AGOSTINO'&nbsp; work... <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; the server error said&nbsp;&nbsp;&nbsp; <br>
    <pre wrap=""><big>ERROR: syntax error at or near "AGOSTINO" at character 187

Second question:
If there is no way to configure PG9.2 to accept this Cain of update
which is the best method to do a downgrade from 9.2 to 9.0 (we are not using any new function)
</big>

thanks in advance is ok?

</pre>
    <br>
    <br>
  </body>
</html>

--------------030103080805040101000202--