On Fri, 3 Oct 2003, Joshua D. Drake wrote:
> > >Yes, please. Please, please do not force all users to accept new > >features in "stable" trees. > > > > > What if the feature does break compatibility with old features? > What if it is "truly" a new feature? > > One example would be that we are considering reworking > pg_dump/restore a bit to support batch uploads and interactive mode. > It would not break compatibility with anything but would > greatly enhance one's ability to actually backup and restore > large volume sets. for stuff like this, why not just break off a gborg project for it, seperate from the distros? We could pull in the changes as beta starts on a dev cycle, but then pg_dump/pg_restore could be maintained on its own release cycle, and you could easily get 'back features' in like this ... ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match