Re: tracking commit timestamps

From: Steve Singer <steve(at)ssinger(dot)info>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Subject: Re: tracking commit timestamps
Date: 2014-11-19 16:30:09
Message-ID: BLU436-SMTP232C315DF42FEC4A945678FDC890@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On 11/19/2014 08:22 AM, Alvaro Herrera wrote:
>
> I think we're overblowing the pg_upgrade issue. Surely we don't need to
> preserve commit_ts data when upgrading across major versions; and
> pg_upgrade is perfectly prepared to remove old data when upgrading
> (actually it just doesn't copy it; consider pg_subtrans or pg_serial,
> for instance.) If we need to change binary representation in a future
> major release, we can do so without any trouble.
>

That sounds reasonable. I am okay with Petr removing the LSN portion
this patch.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2014-11-19 16:41:12 Re: Add shutdown_at_recovery_target option to recovery.conf
Previous Message Tom Lane 2014-11-19 16:23:47 Re: Functions used in index definitions shouldn't be changed

Browse pgsql-www by date

  From Date Subject
Next Message Joshua D. Drake 2014-11-20 16:44:19 Update website to 9.4rc1?
Previous Message Robert Haas 2014-11-19 13:45:41 Re: tracking commit timestamps