Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()

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