From: | Gourish Singbal <gourish(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Fwd: Need HELP - URGENT |
Date: | 2005-10-20 09:10:59 |
Message-ID: | 674d1f8a0510200210u71177e60s4c261562ea9753a2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
---------- Forwarded message ----------
From: Gourish Singbal <gourish(at)gmail(dot)com>
Date: Oct 19, 2005 5:25 PM
Subject: Need HELP - URGENT
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Tom,
Need some help in analyzing the pg_controldata output.
pg_control version number: 72
Catalog version number: 200310211
Database cluster state: in production
pg_control last modified: Wed 19 Oct 2005 02:40:53 AM PDT
Current log file ID: 875
Next log file segment: 165
Latest checkpoint location: 36B/9E7BFAB8
Prior checkpoint location: 36B/94485F20
Latest checkpoint's REDO location: 36B/9E2065F8
Latest checkpoint's UNDO location: 0/0
Latest checkpoint's StartUpID: 69
Latest checkpoint's NextXID: 52699733
*Latest checkpoint's NextOID: 3508694151
*Time of latest checkpoint: Wed 19 Oct 2005 02:37:19 AM PDT
Database block size: 8192
Blocks per segment of large relation: 131072
Maximum length of identifiers: 64
Maximum number of function arguments: 32
Date/time type storage: 64-bit integers
Maximum length of locale name: 128
LC_COLLATE: en_US.UTF-8
LC_CTYPE: en_US.UTF-8
*From Whats given Below i understand that The OID of my database is
3.5Billion and O
IDs are stored as 4-byte integers, and will overflow at 4 billion.*
**
http://www.sql.org/sql-database/postgresql/FAQ/#4.16
We am using Postgresql 7.4.5 version and its a production database.
Are the OIDs going to Overflow ?. if so whats the Solution, Need help,
please.
--
Best,
Gourish Singbal
--
Best,
Gourish Singbal
From | Date | Subject | |
---|---|---|---|
Next Message | Colton A Smith | 2005-10-20 14:23:40 | excluding a table from pg_dump |
Previous Message | Peter Eisentraut | 2005-10-20 08:58:20 | Re: Possible bug in pgAdmin III v1.2.2 |