pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
Cc: Adam Radlowski <adamr@informatyka.gdansk.pl>
Cc: Lista Postgres <pgsql-admin@postgresql.org>
Subject: Re: Should clients warn in case of server version mismatch ?
Date: Fri, 08 Dec 2006 10:16:53 -0500
Message-ID: <5037.1165591013@sss.pgh.pa.us> (raw)
In-Reply-To: <a97c77030612072330j6871a095u1ba469c7eee2e242@mail.gmail.com>
References: <a97c77030612072049q7acab446v6999f892b17a42ee@mail.gmail.com>
	<45790F91.4090404@informatyka.gdansk.pl>
	<a97c77030612072330j6871a095u1ba469c7eee2e242@mail.gmail.com>

"Rajesh Kumar Mallah" <mallah.rajesh@gmail.com> writes:
> IMHO for major version mismatch psql should not present the
> user with a prompt at all as certain commands are most likely
> not work.

The analogy you're drawing with pg_dump is faulty.  There are at least
three good reasons for psql to be more forgiving of version mismatches
than pg_dump is:

1. pg_dump is commonly run noninteractively (eg, from a cron job) where
any mere warning will likely go unnoticed.  So it has to raise a hard
error to get the DBA's attention.  psql's backslash commands are far
less likely to be used noninteractively, and a failure is usually pretty
obvious to a human user.

2. pg_dump is critical: if it dumps an unusable backup due to not
understanding the system catalogs of a newer server, the DBA who needs
that backup later will be badly screwed.  psql's backslash commands,
again, are not so critical.

3. psql offers a pretty decent amount of functionality even if some of
its backslash commands don't work, whereas a dump that is wrong is worse
than useless.  So the use-case for operating with a version mismatch is
much wider for psql.

So I think we have the right tradeoffs in this regard now.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <5037.1165591013@sss.pgh.pa.us>
Permalink:  ../5037.1165591013@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5037.1165591013@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mallah.rajesh@gmail.com, adamr@informatyka.gdansk.pl
  Subject: Re: Should clients warn in case of server version mismatch ?
  In-Reply-To: <5037.1165591013@sss.pgh.pa.us>
  References: <a97c77030612072049q7acab446v6999f892b17a42ee@mail.gmail.com> <45790F91.4090404@informatyka.gdansk.pl> <a97c77030612072330j6871a095u1ba469c7eee2e242@mail.gmail.com> <5037.1165591013@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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