X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5E21CDA339 for ; Wed, 19 Oct 2005 08:55:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41861-01 for ; Wed, 19 Oct 2005 11:55:24 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by svr1.postgresql.org (Postfix) with ESMTP id 2F0AEDA337 for ; Wed, 19 Oct 2005 08:55:25 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id 8so42156nzo for ; Wed, 19 Oct 2005 04:55:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=N4zshNCnNXx2zgUf9UOP1dZ1nLHnzUGepg20vVcqQmxnx5gKNu0LtUi2yi3k/eptmayt2+dRtdjOqfO7TPIEVKbYShAKng5PW2kEekunbihytQ04frAWDITbz74uQkeTemDByxLLUuzUqww1akWnkStYEg+BY0jlA/IqBfhjago= Received: by 10.36.60.12 with SMTP id i12mr454003nza; Wed, 19 Oct 2005 04:55:29 -0700 (PDT) Received: by 10.36.74.15 with HTTP; Wed, 19 Oct 2005 04:55:29 -0700 (PDT) Message-ID: <674d1f8a0510190455k48425e0ds10d549cd433c18f3@mail.gmail.com> Date: Wed, 19 Oct 2005 17:25:29 +0530 From: Gourish Singbal To: pgsql-admin Subject: Need HELP - URGENT MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1478_17259057.1129722929698" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.09 required=5 tests=[AWL=0.038, HTML_60_70=0.027, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200510/217 X-Sequence-Number: 19289 ------=_Part_1478_17259057.1129722929698 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 ------=_Part_1478_17259057.1129722929698 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Tom,
 
Need some help in analyzing the pg_controldata output.
 
pg_control version number:    &nb= sp;       72
Catalog version number: =             &nb= sp; 200310211
Database cluster state:      = ;         in production
pg_contr= ol last modified:         &nbs= p;   Wed 19 Oct 2005 02:40:53 AM PDT
Current log file ID:        &nb= sp;         875
Next log file se= gment:           &nb= sp;    165
Latest checkpoint location:   &= nbsp;       36B/9E7BFAB8
Prior checkpoint = location:           = 36B/94485F20
Latest checkpoint's REDO location:    36B/9= E2065F8
Latest checkpoint's UNDO location:    0/0
Latest chec= kpoint's StartUpID:        69
Latest = checkpoint's NextXID:         = 52699733
Latest checkpoint's NextOID:    &n= bsp;     3508694151
Time of latest checkpoi= nt:            Wed 1= 9 Oct 2005 02:37:19 AM PDT
Database block size:        &nb= sp;         8192
Blocks per segm= ent of large relation: 131072
Maximum length of identifiers:  =       64
Maximum number of function arguments: = 32
Date/time type storage:       &nbs= p;       64-bit integers
Maximum length of locale name:       = ; 128
LC_COLLATE:         &= nbsp;           &nbs= p;     en_US.UTF-8
LC_CTYPE:    =             &nb= sp;            en_US= .UTF-8
 
From Whats given Below i understand that The OID of my da= tabase is 3.5 Billion and OIDs are stored as 4-byte integers= , and will overflow at 4 billion.
 
 

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
------=_Part_1478_17259057.1129722929698--