Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 604B46502EC
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Thu, 24 Jul 2008 16:51:11 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 20320-09 for <pgsql-admin-postgresql.org@postgresql.org>;
	Thu, 24 Jul 2008 16:51:05 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mmp3.nems.noaa.gov (mmp3.nems.noaa.gov [140.90.121.158])
	by postgresql.org (Postfix) with ESMTP id 19EDF6502E4
	for <pgsql-admin@postgresql.org>; Thu, 24 Jul 2008 16:51:05 -0300 (ADT)
Received: from [10.1.10.145] ([192.46.108.142])
	by mmp3.nems.noaa.gov (Sun Java System Messaging Server 6.2-2.05 (built
	Apr 28
	2005)) with ESMTPSA id <0K4J00GM00H2LRC0@mmp3.nems.noaa.gov> for
	pgsql-admin@postgresql.org; Thu, 24 Jul 2008 15:51:03 -0400 (EDT)
Date: Thu, 24 Jul 2008 14:51:03 -0500
From: Chris Bovitz <Christopher.Bovitz@noaa.gov>
Subject: Re: Upgrade clients when (major) upgrading server?
In-reply-to: <dcc563d10807241106xfe8ed3i39a203661736a623@mail.gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Message-id: <4888DD27.6070204@noaa.gov>
Organization: NOAA/NWS/NOHRSC
MIME-version: 1.0
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <488898F0.6010406@noaa.gov>
	<dcc563d10807241106xfe8ed3i39a203661736a623@mail.gmail.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080707)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200807/211
X-Sequence-Number: 29821

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Scott Marlowe wrote:
<blockquote
 cite="mid:dcc563d10807241106xfe8ed3i39a203661736a623@mail.gmail.com"
 type="cite">
  <pre wrap="">On Thu, Jul 24, 2008 at 9:00 AM, Chris Bovitz
<a class="moz-txt-link-rfc2396E" href="mailto:Christopher.Bovitz@noaa.gov">&lt;Christopher.Bovitz@noaa.gov&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">We have 8.1.3 on our operational and development database servers and will
upgrade to 8.3.3 (development) and 8.2.9 (operations) soon.  (We will not
upgrade both systems' databases now because we've already tested 8.2 on our
web server database for the past year, so it's already spent time in
"development.")  I have read through the server upgrade notes, and they seem
to be pretty self-explanatory.  It's even mentioned how to upgrade the
client.  And that's where my questions lie.

The clients on our workstations were installed when our 8.1.3 was installed,
which I was not involved with.  When I do "psql --version" on a client
machine, it says "8.0.3".  When I do this on the server, I get "8.1.3".

Do we need to upgrade the clients?  Should we?  If so to which version?
 What is involved with that?  That is, other than the note in the
upgrade/installation man pages, is there a set of instructions for upgrading
the client-side software?  If we don't have to upgrade now, when would we
have to?  Are there any things to watch for I should be aware of?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
&gt;From the perspective of libpq it's not a huge deal, but psql needs to
match to make the \ commands work properly.  Upgrading the client is
pretty simple.  Remove the old client packages and install the new
ones.
  </pre>
</blockquote>
Does it matter which version - 8.3.3 or 8.2.9 - we install on our
client boxes?&nbsp; Is the client-side backwards compatible?&nbsp; Or should we
install both and have a wrapper for the "psql" script to detect which
database we're going to and use the appropriate binaries?<br>
<br>
<br>
Chris
</body>
</html>