Re: Best practice for long-lived journal tables: bigint or recycling IDs?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Mark Stosberg <mark(at)summersault(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Best practice for long-lived journal tables: bigint or recycling IDs?
Date: 2008-07-08 21:20:13
Message-ID: 20080708212013.GF4095@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Mark Stosberg wrote:
>
> Hello,
>
> I have some tables that continually collect statistics, and then over time are
> pruned as the stats are aggregated into more useful formats.
>
> For some of these tables, it it is fore-seeable that the associated sequences
> would be incremented past the max value of the "int" type in the normal course
> of things.
>
> I see two options to prepare for that:

3. Deal with wraparound by ensuring that the applications behave sanely

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Mark Stosberg 2008-07-08 21:35:24 Re: Best practice for long-lived journal tables: bigint or recycling IDs?
Previous Message Mark Stosberg 2008-07-08 21:16:34 Best practice for long-lived journal tables: bigint or recycling IDs?