Re: Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option.
Date
Msg-id 15169.1208056030@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option.  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
I wrote:
> Silent allow is fine with me, I was just wondering if anyone liked
> the other options better.

Okay, I'm back on the warpath about this after noting yet another user
who thinks he should use -i mindlessly:
http://archives.postgresql.org/pgsql-admin/2008-04/msg00111.php

I believe the consensus was

* pg_dump and pg_restore should continue to accept -i/--ignore-version
options, to avoid needlessly breaking existing scripts, but these
switches will become no-ops; the version check will occur anyway.

* pg_dump should be fixed to allow server minor version greater than its
own, but not server major version.

Last chance for objections...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cached Query Plans (was: global prepared statements)
Next
From: "Jonah H. Harris"
Date:
Subject: Re: Cached Query Plans (was: global prepared statements)