| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Removing pg_migrator limitations |
| Date: | 2009-12-27 20:35:37 |
| Message-ID: | 407d949e0912271235i73bd5be4k60d85b9bd1ef72b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 27, 2009 at 8:13 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Well, I think the checksums are going in the item pointers, so there
> isn't any new storage space --- my guess is that the page version number
> will control how the backend stores the checksum. Basically the backend
> will need to read old and new page versions. I don't think this is
> something pg_migrator can handle cleanly.
I thought our plan was to only read old page versions and
automatically rewrite them to new page versions. We'll have to add the
hooks and the page rewrite code to do that, no?
Is that something we're comfortable adding in the final commitfest?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-27 21:29:28 | Re: parse_oper cache |
| Previous Message | Andres Freund | 2009-12-27 20:20:01 | Re: Small Bug in GetConflictingVirtualXIDs |