Thanks for your answer. Is there any other risk than wrong answers when
running with wrong locale?
So maybe the best bet would be:
1) drop all text/varchar user indexes
2) stop database, change the locale
3) in single user mode reindex shared tables and system tables in all
databases and
Hi,
we've made mistake and initdb database cluster in wrong locale :-(
Now it's full of data. I've read in the docs that it's not possible to
change locale.
But I guess something like this would work:
a)
1) drop all indexes on text/varchar columns
2) change cluster locale
3) create all
On Mon, Feb 19, 2007 at 09:27:06AM +0100, Jakub Ouhrabka wrote:
But I guess something like this would work:
a)
1) drop all indexes on text/varchar columns
2) change cluster locale
3) create all indexes on text/varchar columns
You're going to miss the name columns, ie. every string index in
Martijn van Oosterhout kleptog@svana.org writes:
But I guess something like this would work:
1) drop all indexes on text/varchar columns
2) change cluster locale
3) create all indexes on text/varchar columns
You're going to miss the name columns, ie. every string index in
pg_catalog.
But
Hi Tom,
Hacking pg_control would be the hard part; you'll never get the CRC
right if you do it manually. Possibly pg_resetxlog could be adapted
to the purpose.
thanks for your valuable answer! I looked at pg_resetxlog.c but I'm no
pg internals' expert - would something like this work?
1)
