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

From Marko Tiikkaja
Subject Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Date
Msg-id 08129d47-7952-dff2-e9e9-8a1b2bf706bd@joh.to
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
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

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()