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

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Keith Fiske <keith(at)omniti(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 21:03:22
Message-ID: 08129d47-7952-dff2-e9e9-8a1b2bf706bd@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2016-09-13 22:58, Keith Fiske wrote:
> No, it's obtained elsewhere by querying the current max timestamp value
> from the partition set.
> Shouldn't matter if it was, though. You can see that all it takes to change
> the string output of the timestamp is swapping the values around. The
> values of the variables are the same in either case.

Did you miss this part?

/* [ ... ] Note
* also that the result is in a static buffer, not pstrdup'd.
*/

.m

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Keith Fiske 2016-09-13 21:06:16 Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Previous Message Keith Fiske 2016-09-13 20:58:01 Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()