Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str() - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Date
Msg-id 28770.1473799942@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()  (Keith Fiske <keith@omniti.com>)
Responses Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()  (Keith Fiske <keith@omniti.com>)
List pgsql-bugs
Keith Fiske <keith@omniti.com> writes:
> Ok, this may be more of an actual issue than I thought. It seems that, even
> if all variables to the timestamptz_to_str() function have a valid value
> set, if it is called multiple times in the same statement, it keeps the
> first value for all following occurrences.

What is current_partition_timestamp?  Is it coming from the transaction
timestamp?  That doesn't change intra-statement ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Keith Fiske
Date:
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Next
From: Keith Fiske
Date:
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()