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

From Keith Fiske
Subject Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Date
Msg-id CAG1_KcCkcUYaZmNz6ot9GJrtYNur0KOz7QhiUF6FZDC16XZ9+w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()  (Marko Tiikkaja <marko@joh.to>)
Responses Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Sep 13, 2016 at 5:03 PM, Marko Tiikkaja <marko@joh.to> wrote:

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

Yeah I did see that when i went to look at its source and wondered if that
may be why, but I'm still fairly new to C and wasn't sure that was the
reason.
Still think it would be nice to use it in a more flexible manner.

pgsql-bugs by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Next
From: Tom Lane
Date:
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()