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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Keith Fiske <keith(at)omniti(dot)com>
Cc: Keith <keith(at)keithf4(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Date: 2016-09-13 20:52:22
Message-ID: 28770.1473799942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Keith Fiske <keith(at)omniti(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Keith Fiske 2016-09-13 20:58:01 Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Previous Message Peter Eisentraut 2016-09-13 20:52:14 Re: [BUGS] BUG #14244: wrong suffix for pg_size_pretty()