Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id E45A79FB5D0 for ; Fri, 27 Jul 2007 11:49:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 57378-02 for ; Fri, 27 Jul 2007 11:49:29 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by postgresql.org (Postfix) with ESMTP id BF2749FB540 for ; Fri, 27 Jul 2007 11:49:35 -0300 (ADT) Received: from YZANGXP ([192.168.124.31]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Jul 2007 10:49:33 -0400 From: "George Wilk" To: Cc: "'Gez Saunders'" Subject: Checking database version Date: Fri, 27 Jul 2007 10:49:30 -0400 Message-ID: <02b201c7d05d$56cf9890$1f7ca8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02B3_01C7D03B.CFBDF890" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: AcfQXVanZV9xwJEgT8qiR9bn5Arcew== X-OriginalArrivalTime: 27 Jul 2007 14:49:33.0570 (UTC) FILETIME=[5852B620:01C7D05D] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1021-15324.003 X-TM-AS-Result: No--6.603300-4.000000-1 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/310 X-Sequence-Number: 26291 This is a multi-part message in MIME format. ------=_NextPart_000_02B3_01C7D03B.CFBDF890 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Is there a reliable way of verifying version of the database by looking at the PGDATA directory? Let me explain why this is important in our case. Originally, our product utilized version 8.1 of Postgres. We have since moved on to version 8.2. Our existing customer base will need to be upgraded to version 8.2 as well. There might be legitimate cases where our customers might be running other software products on their systems, which utilize earlier versions of Postgres, therefore we cannot uninstall earlier packages and install ours indiscriminately. Our install scripts must reliably determine if the database files related to our product need to be upgraded or not, before installing Postgres 8.2 package, performing dump, etc. What I'm looking for is a sure way of determining version of Postgres based on the files contained in a specific PGDATA location. Is it possible, and if so how can it be done? Thanks in advance, ~george ------=_NextPart_000_02B3_01C7D03B.CFBDF890 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Is there a reliable way of verifying version of the = database by looking at the PGDATA directory?

 

Let me explain why this is important in our = case.  Originally, our product utilized version 8.1 of Postgres.  We have since moved = on to version 8.2.  Our existing customer base will need to be upgraded = to version 8.2 as well.  There might be legitimate cases where our = customers might be running other software products on their systems, which utilize = earlier versions of Postgres, therefore we cannot uninstall earlier packages and install ours indiscriminately.  Our install scripts must reliably determine if the database files related to our product need to be = upgraded or not, before installing Postgres 8.2 package, performing dump, = etc.

 

What I’m looking for is a sure way of = determining version of Postgres based on the files contained in a specific PGDATA = location.  Is it possible, and if so how can it be = done?

 

Thanks in advance,

~george

------=_NextPart_000_02B3_01C7D03B.CFBDF890--