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

From Tom Lane
Subject Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Date
Msg-id 17047.1473801698@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()  (Keith Fiske <keith@omniti.com>)
List pgsql-bugs
Keith Fiske <keith@omniti.com> writes:
> On Tue, Sep 13, 2016 at 5:03 PM, Marko Tiikkaja <marko@joh.to> wrote:
>> Did you miss this part?
>> /* [ ... ] Note
>> * also that the result is in a static buffer, not pstrdup'd.

Oh, duh.

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

You can pstrdup its result if you want.  If it did that internally
it would result in some memory leaks we didn't want, IIRC.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Keith Fiske
Date:
Subject: Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Next
From: Andreas Papst
Date:
Subject: Re: BUG #14320: systemd terminates postgresql hot standby instance 90 seconds after start