pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Upgrade clients when (major) upgrading server?
4+ messages / 2 participants
[nested] [flat]

* Upgrade clients when (major) upgrading server?
@ 2008-07-24 15:00 Chris Bovitz <Christopher.Bovitz@noaa.gov>
  2008-07-24 18:06 ` Re: Upgrade clients when (major) upgrading server? Scott Marlowe <scott.marlowe@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Chris Bovitz @ 2008-07-24 15:00 UTC (permalink / raw)
  To: pgsql-admin

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?

Thanks.


Chris




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrade clients when (major) upgrading server?
  2008-07-24 15:00 Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
@ 2008-07-24 18:06 ` Scott Marlowe <scott.marlowe@gmail.com>
  2008-07-24 19:51   ` Re: Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
  0 siblings, 1 reply; 4+ messages in thread

From: Scott Marlowe @ 2008-07-24 18:06 UTC (permalink / raw)
  To: Chris Bovitz <Christopher.Bovitz@noaa.gov>; +Cc: pgsql-admin

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?



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrade clients when (major) upgrading server?
  2008-07-24 15:00 Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
  2008-07-24 18:06 ` Re: Upgrade clients when (major) upgrading server? Scott Marlowe <scott.marlowe@gmail.com>
@ 2008-07-24 19:51   ` Chris Bovitz <Christopher.Bovitz@noaa.gov>
  2008-07-24 20:13     ` Re: Upgrade clients when (major) upgrading server? Scott Marlowe <scott.marlowe@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Chris Bovitz @ 2008-07-24 19:51 UTC (permalink / raw)
  To: Scott Marlowe <scott.marlowe@gmail.com>; +Cc: pgsql-admin

<!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>



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrade clients when (major) upgrading server?
  2008-07-24 15:00 Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
  2008-07-24 18:06 ` Re: Upgrade clients when (major) upgrading server? Scott Marlowe <scott.marlowe@gmail.com>
  2008-07-24 19:51   ` Re: Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
@ 2008-07-24 20:13     ` Scott Marlowe <scott.marlowe@gmail.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Scott Marlowe @ 2008-07-24 20:13 UTC (permalink / raw)
  To: Chris Bovitz <Christopher.Bovitz@noaa.gov>; +Cc: pgsql-admin

On Thu, Jul 24, 2008 at 1:51 PM, Chris Bovitz
<Christopher.Bovitz@noaa.gov> wrote:
>
>
> Does it matter which version - 8.3.3 or 8.2.9 - we install on our client
> boxes?  Is the client-side backwards compatible?  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?

psql itself is not backwards / forwards compatible.  libpq is.  So if
you need to talk to 8.2 and 8.3 databases from psql, then it's a good
idea to have both.



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2008-07-24 20:13 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-07-24 15:00 Upgrade clients when (major) upgrading server? Chris Bovitz <Christopher.Bovitz@noaa.gov>
2008-07-24 18:06 ` Scott Marlowe <scott.marlowe@gmail.com>
2008-07-24 19:51   ` Chris Bovitz <Christopher.Bovitz@noaa.gov>
2008-07-24 20:13     ` Scott Marlowe <scott.marlowe@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox