Re: tracking commit timestamps - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: tracking commit timestamps
Date
Msg-id 20141119132207.GB1639@alvin.alvh.no-ip.org
Whole thread Raw
In response to Re: tracking commit timestamps  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: tracking commit timestamps  (Robert Haas <robertmhaas@gmail.com>)
Re: tracking commit timestamps  (Steve Singer <steve@ssinger.info>)
List pgsql-hackers
Petr Jelinek wrote:

> This is good point, we are not too late in the cycle that LSN couldn't be
> added later if we find that it is indeed needed (and we don't have to care
> about pg_upgrade until beta).

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.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Add shutdown_at_recovery_target option to recovery.conf
Next
From: Robert Haas
Date:
Subject: Re: Doing better at HINTing an appropriate column within errorMissingColumn()