Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs
Date: 2011-12-01 07:21:41
Message-ID: 1322724101.24279.26.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 2011-11-30 at 20:10 -0500, Tom Lane wrote:
> I believe what is happening in the second case is that the query is
> getting re-parse-analyzed, from scratch, and since now datestyle is
> different (DMY not MDY), the date literal gets interpreted differently.
> You could argue it either way as to which result is "more correct",
> but I doubt we're going to try to do something about that. Best advice
> is to avoid ambiguous input, or if you can't, at least avoid flipping
> your datestyle on the fly.

I'm fine calling that "not a bug", though it appears to work in 8.3.

Regards,
Jeff Davis

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Josh Kupershmidt 2011-12-01 14:06:57 Re: 9.1.1 hot standby startup gets sigbus
Previous Message Bèrto ëd Sèra 2011-12-01 07:18:10 Re: transaction error handling