| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | "Massa, Harald Armin" <chef(at)ghum(dot)de> |
| Subject: | Re: overwrite the encoding of a database |
| Date: | 2009-07-16 09:24:59 |
| Message-ID: | 200907161125.00004.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday 16 July 2009 10:53:37 Massa, Harald Armin wrote:
> Hello,
>
> I have an old PostgreSQL Database which was created with encoding =
> SQL_ASCII. That is an old sin of mine; 9years ago I did not know better.
>
> Now I know better than to use SQL_ASCII.
>
> On the bright side: I am totally sure that the TEXT within that database is
> in WIN1252 / CP1252 encoding.
>
> Is there any way to overwrite the encoding-information? something like
> "udpate <specialsystemcatalog> set pg_encodingcol='xxx' where
> databasename='oldsin';
Would a dump+reload work?
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Weimer | 2009-07-16 09:28:45 | Working around spurious unique constraint errors due to SERIALIZABLE bug |
| Previous Message | Arndt Lehmann | 2009-07-16 09:22:26 | Re: best practice transitioning from one datatype to another |