From: | Jonathan Bartlett <johnnyb6(at)sdf(dot)lonestar(dot)org> |
---|---|
To: | Nicolas Huillard <nhuillard(at)ghs(dot)fr> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: PostgreSQL 7.1 and ORACLE 8.x |
Date: | 2001-06-08 15:31:11 |
Message-ID: | Pine.LNX.4.21.0106081528500.9063-100000@sdf.lonestar.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Earlier posts by Tom Lane indicated that when 32 bits are taken up, you
have to dump/restore your database (actually, you have to do that before
they are all gone).
Gnome calculator shows 2^32 being 4,294,967,296, or roughly 4 billion
transactions. This doesn't really matter in the medium-size database
department (if you get there let me know), but in the higher-end it could
be a problem.
Tom suggested a dump/restore when pg_log got near 1 gig.
Jon
johnnyb6(at)sdf(dot)lonestar(dot)org
SDF Public Access UNIX System - http://sdf.lonestar.org
On Fri, 8 Jun 2001, Nicolas Huillard wrote:
> > No limit on #transactions before dump/restore
>
> What is that limit ? Is Postgres limited in such way ?
>
> NH
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2001-06-08 15:37:28 | Re: 7.1 upgrade problems |
Previous Message | Vivek Khera | 2001-06-08 15:27:05 | Re: very big problem with NULL |