|
Home > Archive > PostgreSQL Administration > November 2006 > running initdb on running database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
running initdb on running database
|
|
|
|
| Jim C. Nasby 2006-11-14, 7:19 pm |
| On Mon, Nov 13, 2006 at 03:10:14PM -0600, Ben K. wrote:
>
> Admins,
>
> I'm reading this post:
>
> http://archives.postgresql.org/pgsq...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)
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly
| |
| Ben K. 2006-11-14, 7:19 pm |
| On Tue, 14 Nov 2006, Jim C. Nasby wrote:
> On Mon, Nov 13, 2006 at 03:10:14PM -0600, Ben K. wrote:
> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
|
|
|
|