possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs
Date: 2011-11-30 21:59:17
Message-ID: CAMp0ubdWEv63h4x_cap_LKUcXGcbS7++3GyQaJrMq9pAHVCoSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
    text
------------
 02-01-2011
(1 row)

SET
    text
------------
 01-02-2011
(1 row)

DEALLOCATE

But with -DCLOBBER_CACHE_ALWAYS and -DRELCACHE_FORCE_RELEASE, I get:

SET
PREPARE
     text
------------
 02-01-2011
(1 row)

SET
    text
------------
 02-01-2011
(1 row)

DEALLOCATE

Which one of those results is correct?

Regards,
Jeff Davis

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2011-11-30 23:36:54 Re: transaction error handling
Previous Message Robert Haas 2011-11-30 20:36:11 Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails