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-06 01:29:27
Message-ID: CAMp0ubdy2Am4jA7ri875VJ6-9FR7TkkR7Lx3Kjvak+aFukG_-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 30, 2011 at 5:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The result of parse analysis for that query is a stored date constant
> (in a Const node) with a cast-to-text on top of it.  The system is aware
> that cast-date-to-text isn't immutable, so it doesn't try to fold the
> cast operation.  When you execute the query, it displays the date
> constant using the now-current datestyle.

Another thought: why does it execute the type input function (which is
dependent on a GUC), but not the cast?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-12-06 05:35:59 Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs
Previous Message Euler Taveira de Oliveira 2011-12-05 16:28:37 Re: BUG #6327: Prefix full-text-search fails for hosts with complicated names