| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: #postgresql report |
| Date: | 2004-06-15 17:20:41 |
| Message-ID: | 20040615142005.H1028@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 15 Jun 2004, Peter Eisentraut wrote:
> Christopher Kings-Lynne wrote:
>> * We have a request for how to change database encoding every other
>> day
>
> This is pretty much impossible. It's analogous to changing, say, the
> endianness of all integers. You would need to rewrite the entire
> database. But pg_dump & restore already does that.
Just a thought here ... but, how about some sort of CREATE DATABASE
extension that would transparently do the dump/restore, with the restore
based on the new encoding?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-06-15 17:43:20 | Re: #postgresql report |
| Previous Message | Marc G. Fournier | 2004-06-15 17:07:57 | Re: 7.4.3 running a bit late ... |