Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group