X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 7E9159FB1CF for ; Tue, 2 May 2006 11:07:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 05577-08 for ; Tue, 2 May 2006 11:07:30 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.204]) by postgresql.org (Postfix) with ESMTP id 49EF79FA25D for ; Tue, 2 May 2006 11:07:30 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id m7so2731978nzf for ; Tue, 02 May 2006 07:07:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=puMfenDBMJoGWyMK2smPA+e9LmcA37TND47HaIFrAde0vA3q1myJYCFbigrepubJNhv68YhXzw8cF8lo68VxXsPrWrqf2H1dxbPOVGgOSozSLZnh0MMkFVnmxQLNCZK+scbSQgolSuSe7C3Kdfr1mT+TdXRU2et2EOcFjFvlg1w= Received: by 10.65.150.15 with SMTP id c15mr406383qbo; Tue, 02 May 2006 07:07:27 -0700 (PDT) Received: by 10.65.249.3 with HTTP; Tue, 2 May 2006 07:07:27 -0700 (PDT) Message-ID: Date: Tue, 2 May 2006 19:07:27 +0500 From: "Shoaib Mir" To: pgsql-admin@postgresql.org Subject: Re: Modifying the encoding of a database In-Reply-To: <002501c66df1$23399500$4700a8c0@TREEZANTHUS> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34569_19791327.1146578847177" References: <002501c66df1$23399500$4700a8c0@TREEZANTHUS> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/16 X-Sequence-Number: 21548 ------=_Part_34569_19791327.1146578847177 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I dont think so you can modify the database encoding ... solution would be recreate it with the changed encoding /Shoaib On 5/2/06, Rodrigo Sakai wrote: > > Hi, > > Is it possible to modify the encoding of a production database? Or the > only way is to create a new database with the correct enconding??? > > Thanks! > ------=_Part_34569_19791327.1146578847177 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I dont think so you can modify the database encoding ... solution would be = recreate it with the changed encoding

/Shoaib

On 5/2/06, Rodrigo Sakai <rodrigo.sakai@zanthus.com.br> wrote:
  Hi,
 
  Is it possible to modify the en= coding of a=20 production database? Or the only way is to create a new database with the= =20 correct enconding???
 
  Thanks!

------=_Part_34569_19791327.1146578847177--