Re: Discontent with development process (was:Re: pgaccess - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Discontent with development process (was:Re: pgaccess
Date
Msg-id GNELIHDDFBOCMGBFGEFOCEJICCAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: Discontent with development process (was:Re: pgaccess  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
> Actually, even for those that wuldn't need the patch ... as long as the
> "default behaviour" doesn't change, and unless there are no valid
> technical arguments around it, there is no reason why a patch shouldn't be
> included ...

Unless it's going to interfere with implementing the general case in the
future, making it a painful feature to keep backwards-compatibility with.
Which is what the discussion was about IIRC...

Chris



pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Discontent with development process (was:Re: pgaccess
Next
From: Oliver Elphick
Date:
Subject: Re: pg_dump DROP commands and implicit search paths