Re: pg_migrator to /contrib in a later 9.0 beta

From: Jesper Krogh <jesper(at)krogh(dot)cc>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_migrator to /contrib in a later 9.0 beta
Date: 2010-05-05 18:55:10
Message-ID: 4BE1BF0E.6020808@krogh.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2010-05-03 23:09, Bruce Momjian wrote:
> Robert Haas wrote:
>
>> On Sun, May 2, 2010 at 3:45 PM, Dimitri Fontaine<dfontaine(at)hi-media(dot)com> wrote:
>>
>>> Now you tell me how awful this idea really is :)
>>>
>> I'm not sure I can count that high. :-)
>>
> While I can't improve on Robert's reply, I can supply a PDF about how
> pg_migrator works:
>
> http://momjian.us/main/presentations/technical.html#pg_migrator
>
>
There is a huge amount of users to whom pg_migrator is "at least"
a big a feature as HS+SR is.

Last dump/restore was a 24 hours process in one of our installations.
I think it was due to in-efficiency in handling BYTEA types in the
process (but not sure).

But I'm one of the few guys who seem to have an infinite amount of
time for reading on mailing lists, but without my knowledge from
reading this list I would never have run pg_migrator on my production
data if I had to pick it from pg_foundry.

Just my 0.25€

Jesper
--
Jesper

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-05-05 20:49:25 Re: max_standby_delay considered harmful
Previous Message Pavel Stehule 2010-05-05 18:42:01 patch: to_string, to_array functions