Le jeudi 31 janvier 2008, Tom Lane a écrit : > I'm thinking next major. In principle there could be cases where a > minor update could break pg_dump, but it seems unlikely enough that > it's not reasonable to embed such a policy in the code. As for > next major, though, the mere existence of the -i switch is a foot-gun > with no significant value.
+2 then :)
1. Current behavior is to issue the « -i warning » even when having minor
version mismatch, getting rid of this would be great... even more so now
we know there's almost no risk here.
2. Major version mismatch seems to be one of the major migration pitfalls out
there. The famous "You have to dump with the newer pg_dump version against
the current production setup" cookbook entry will certainly be better
embedded into the code.
Regards,
--
dim
signature.asc
Description: This is a digitally signed message part.
