Re: tracking commit timestamps - Mailing list pgsql-hackers

From Steve Singer
Subject Re: tracking commit timestamps
Date
Msg-id BLU436-SMTP232C315DF42FEC4A945678FDC890@phx.gbl
Whole thread Raw
In response to Re: tracking commit timestamps  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: tracking commit timestamps  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Functions used in index definitions shouldn't be changed
Next
From: Fujii Masao
Date:
Subject: Re: Add shutdown_at_recovery_target option to recovery.conf