Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 124CD6502EC
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Thu, 24 Jul 2008 15:06:16 -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 30732-01 for <pgsql-admin-postgresql.org@postgresql.org>;
	Thu, 24 Jul 2008 15:06:11 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.226])
	by postgresql.org (Postfix) with ESMTP id DAE41650217
	for <pgsql-admin@postgresql.org>; Thu, 24 Jul 2008 15:06:12 -0300 (ADT)
Received: by qb-out-0506.google.com with SMTP id d8so4537956qbc.23
	for <pgsql-admin@postgresql.org>; Thu, 24 Jul 2008 11:06:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=7woz7nUxywH1rW7738y3NekyXtOQaW8F+eHu2WoEHgc=;
	b=JUlsggwRtexnw9kHDgdE4LmSLDQlcyqkPdtT4fJevsJJLOvTejdoNw6txG0MSCz/JI
	NRNb3xUT12wsSZN/XjnTOsvtr8SgaValCE/ON49AV2d4VQmTUcx6HfsukiVSjS+HP2jj
	ymmZRWPpXTtuG+vw54o0MRa3JmgMRuel/oTDE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=q4GTL1K5BLqmYJRwTV4Kk4/eafgJaj7Ds80G84kHSXI1YvMV0t+33WI73U0ujBjYc/
	uSdGg6+uqTM8seYsmHWJqI8zeQ4/HEsYWCdQ3bdE71SgK1ahnjFsBukKDfV/LGCsIpFK
	hoJzyq3Nli0WTvTVgl9PCcSy7V1GLYqzZaI6o=
Received: by 10.142.173.14 with SMTP id v14mr190602wfe.315.1216922771209;
	Thu, 24 Jul 2008 11:06:11 -0700 (PDT)
Received: by 10.142.158.14 with HTTP; Thu, 24 Jul 2008 11:06:11 -0700 (PDT)
Message-ID: <dcc563d10807241106xfe8ed3i39a203661736a623@mail.gmail.com>
Date: Thu, 24 Jul 2008 12:06:11 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Chris Bovitz" <Christopher.Bovitz@noaa.gov>
Subject: Re: Upgrade clients when (major) upgrading server?
Cc: pgsql-admin@postgresql.org
In-Reply-To: <488898F0.6010406@noaa.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <488898F0.6010406@noaa.gov>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200807/209
X-Sequence-Number: 29819

On Thu, Jul 24, 2008 at 9:00 AM, Chris Bovitz
<Christopher.Bovitz@noaa.gov> wrote:
> 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?