Jeff Amiel writes:
> It's come time to bite the bullet and convert a half-terraybyte database
> from ASCII to UTF8. Have gone through a bit of effort to track down the
> unclean ascii text and repair it but would like to avoid the outage of a
> many-many hour dump-restore.
Those blog articles of
On Wed, Feb 23, 2011 at 9:06 AM, Geoffrey Myers
wrote:
> I'm assuming you're saying you can replicate from an ASCII database to UTF8?
> What happens to the data that is not UTF8 'friendly?'
>
The assumption up-thread was that the data was already made UTF8
friendly in the US_ASCII database.
--
Vibhor Kumar wrote:
On Feb 22, 2011, at 10:23 PM, Jeff Amiel wrote:
It's come time to bite the bullet and convert a half-terraybyte database from
ASCII to UTF8. Have gone through a bit of effort to track down the unclean
ascii text and repair it but would like to avoid the outage of a many-m
On Tue, Feb 22, 2011 at 11:53 AM, Jeff Amiel 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 correctl
On Feb 22, 2011, at 10:23 PM, Jeff Amiel wrote:
> It's come time to bite the bullet and convert a half-terraybyte database from
> ASCII to UTF8. Have gone through a bit of effort to track down the unclean
> ascii text and repair it but would like to avoid the outage of a many-many
> hour dump
It's come time to bite the bullet and convert a half-terraybyte database from
ASCII to UTF8. Have gone through a bit of effort to track down the unclean
ascii text and repair it but would like to avoid the outage of a many-many hour
dump-restore.
Using Postgres 8.4.X.
Are there any other magi
