On Fri, Aug 13, 2021 at 12:25:00AM +0100, Simon Riggs wrote:
> > > I thought we found that changing behavior via GUC usually ends badly.
> >
> > Yeah. Changing from SQL-spec to not-SQL-spec behavior is going to be
> > one tough sell to begin with, even without the point that that's been
> > our behavior for over two decades. But proposing to do it via a GUC
> > is just not-even-worth-discussing territory. That would force every
> > wannabe-portable program to cope with both behaviors; which would
> > end up meaning that not only do you still have to take care to write
> > WITH TIME ZONE when you want that, but *also* you'd have to be sure
> > to write WITHOUT TIME ZONE when you want that. In short, the worst
> > of both worlds.
>
> All of which I agree with, but this wasn't a cute idea of mine, this
> was what our users have requested because of the extreme annoyance
> caused by the current behavior.
Understood, but the problem is that our users sometimes don't think
through the ramifications of their suggestions.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
