| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, 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-02 19:34:29 |
| Message-ID: | 201005021934.o42JYTf24348@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
> > For example, I assume there
> > will be some major version of Postgres where pg_migrator will not work
> > at all.
> >
> >
>
> We need to be thinking more now about such a contingency. Postgres use
> in very large installations is now at such a level that requiring a
> pg_dump/pg_restore is really not an option for many users. If
> pg_migrator is not always going to work then we need to be addressing
> that now, or else it is at best a stop-gap. ISTM some sort of page
> layout versioning scheme might be at least part of what we'll need in
> the medium term.
Yes, my bet is that when we do need to change the page format, we will
either use a conversion-on-read process or some external tool to do the
conversion. pg_migrator does have code to do page conversions but it
has never been used. If you are using pg_migrator in copy mode, we
might be able to do page conversion during the copy, but for link mode,
that is not possible.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-05-02 19:45:33 | Re: pg_migrator to /contrib in a later 9.0 beta |
| Previous Message | Andrew Dunstan | 2010-05-02 19:30:37 | Re: pg_migrator to /contrib in a later 9.0 beta |