From: Ben K. <bkim@coe.tamu.edu>
To: Jim C. Nasby <jim@nasby.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: running initdb on running database
Date: Tue, 14 Nov 2006 13:15:46 -0600 (CST)
Message-ID: <Pine.GSO.4.64.0611141309380.19061@coe.tamu.edu> (raw)
In-Reply-To: <20061114171715.GX90133@nasby.net>
References: <Pine.GSO.4.64.0611131502290.1474@coe.tamu.edu>
<20061114171715.GX90133@nasby.net>
On Tue, 14 Nov 2006, Jim C. Nasby wrote:
> On Mon, Nov 13, 2006 at 03:10:14PM -0600, Ben K. wrote:
>> Admins,
>> I'm reading this post:
>> http://archives.postgresql.org/pgsql-novice/2005-04/msg00221.php
>> Is it possible and safe to run initdb again on a running database to
>> change encoding from SQL_ASCII to UTF8?
>> Will it affect new databases only or existing databases as well?
> Pretty much guaranteed to be unsafe. It's also not possible unless you
> hack initdb.
> --
> Jim Nasby jim@nasby.net
> EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Thanks.
I guess then the next upgrade may be the best opportunity to change the
encoding.
Regards,
Ben K.
Developer
http://benix.tamu.edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bkim@coe.tamu.edu, jim@nasby.net
Subject: Re: running initdb on running database
In-Reply-To: <Pine.GSO.4.64.0611141309380.19061@coe.tamu.edu>
References: <Pine.GSO.4.64.0611131502290.1474@coe.tamu.edu> <20061114171715.GX90133@nasby.net> <Pine.GSO.4.64.0611141309380.19061@coe.tamu.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox