| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | Jeff Amiel <becauseimjeff(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Covert database from ASCII to UTF-8 |
| Date: | 2011-02-22 17:08:09 |
| Message-ID: | AANLkTimKMcLoq7xf=UkREmVbR6jA6vvFM_4VeUPuNm4n@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 22, 2011 at 11:53 AM, Jeff Amiel <becauseimjeff(at)yahoo(dot)com> wrote:
> I assume slony replication is an option.....
this is my plan, once i finish cleaning up the code and the DB data.
you have to ensure that whatever the original DB emits (in the form of
COPY and individual updates later on) will import correctly into the
new DB without error, else you're hosed.
also, I'd do it one table at a time rather than all at once, to
minimize failure cases if there is a problem with one table.
> What about some sort of wal log shipping replication?
>
I don't think you can do that. This is a binary replication that
copies disk pages.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Kerr | 2011-02-22 17:13:52 | Re: Reordering a table |
| Previous Message | Tom Lane | 2011-02-22 17:06:14 | Re: work_mem = 900MB but Sort Method: external merge Disk: 304008kB |