possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs - Mailing list pgsql-bugs

From Jeff Davis
Subject possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs
Date
Msg-id CAMp0ubdWEv63h4x_cap_LKUcXGcbS7++3GyQaJrMq9pAHVCoSA@mail.gmail.com
Whole thread Raw
Responses Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
SQL:

  set datestyle to postgres,us;
  prepare stmt as select '02-01-2011'::date::text;
  execute stmt;
  set datestyle to postgres,euro;
  execute stmt;
  deallocate stmt;

The results I get with normal debug compilation are:

  SET
  PREPARE
  =A0=A0=A0 text
  ------------
  =A002-01-2011
  (1 row)

  SET
  =A0=A0=A0 text
  ------------
  =A001-02-2011
  (1 row)

  DEALLOCATE

But with -DCLOBBER_CACHE_ALWAYS and -DRELCACHE_FORCE_RELEASE, I get:

  SET
  PREPARE
=A0  =A0=A0 text
  ------------
  =A002-01-2011
  (1 row)

  SET
  =A0=A0=A0 text
  ------------
  =A002-01-2011
  (1 row)

  DEALLOCATE

Which one of those results is correct?

Regards,
    Jeff Davis

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails
Next
From: Tom Lane
Date:
Subject: Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs