| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>, Adam Radlowski <adamr(at)informatyka(dot)gdansk(dot)pl>, Lista Postgres <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Should clients warn in case of server version mismatch |
| Date: | 2006-12-08 16:33:04 |
| Message-ID: | 1165595584.3243.45.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2006-12-08 at 09:16, Tom Lane wrote:
> "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)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:
One more difference, pg_dump is backward compatible. i.e. you don't
have to use the -i switch to run pg_dump v 8.1.x against pgsql v < 8.1
because pg_dump knows how to back up older version of the db on
purpose. So, pg_dump is VERY forgiving going in one direction, as it
should be, and very unforgiving going in the other, again, as it should
be.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2006-12-08 17:25:50 | Re: tsearch2 problem rank_cd() (possibly) crashing postgres |
| Previous Message | Joshua D. Drake | 2006-12-08 16:18:42 | Re: tsearch2 problem rank_cd() (possibly) crashing postgres |