David G. Johnston wrote:
> This bug has an obvious if annoying work-around and fixing the bug will
> likely cause people's code, that uses said work-around, to fail. Breaking
> people's working code in stable release branches is generally a no-no.
>
> However, given that this was discovered 4 months after the feature was
> released suggests to me that we are justified, and community-serving, to
> back-patch this. Put more bluntly, we can ask for more leeway in the first
> few patch releases of a new feature since more people will benefit from 5
> years of a fully-baked feature than may be harmed by said change. We
> shouldn't abuse that but an obvious new feature bug/oversight like this
> seems reasonable.
I agree with this argumentation and in my opinion we should back-patch
this as a bugfix. Certainly if I had remembered about CREATE TABLE LIKE
I would have stalled the ext.stats patch.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
