Re: tracking commit timestamps - Mailing list pgsql-hackers

From Robert Haas
Subject Re: tracking commit timestamps
Date
Msg-id CA+TgmoYhAL0_O5XguN51EW-GA32N0J_yWDTcD0pE=8RFvFBH3g@mail.gmail.com
Whole thread Raw
In response to Re: tracking commit timestamps  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: tracking commit timestamps  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Sun, Nov 9, 2014 at 8:41 PM, Alvaro Herrera <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: tracking commit timestamps
Next
From: Robert Haas
Date:
Subject: Re: tracking commit timestamps