Re: tracking commit timestamps

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, 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>, Simon Riggs <simon(at)2ndquadrant(dot)com>, 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-10 13:25:30
Message-ID: CA+TgmoYhAL0_O5XguN51EW-GA32N0J_yWDTcD0pE=8RFvFBH3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On Sun, Nov 9, 2014 at 8:41 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Robert Haas wrote:
>> I think the key question here is the time for which the data needs to
>> be retained. 2^32 of anything is a lot, but why keep around that
>> number of records rather than more (after all, we have epochs to
>> distinguish one use of a given txid from another) or fewer?
>
> The problem is not how much data we retain; is about how much data we
> can address.

I thought I was responding to a concern about disk space utilization.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-11-10 13:26:17 Re: tracking commit timestamps
Previous Message Petr Jelinek 2014-11-10 13:24:58 Re: tracking commit timestamps

Browse pgsql-www by date

  From Date Subject
Next Message Robert Haas 2014-11-10 13:26:17 Re: tracking commit timestamps
Previous Message Petr Jelinek 2014-11-10 13:24:58 Re: tracking commit timestamps