Re: BUG #9849: walreceiver's DEBUG message reports wrong timestamp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: harukat(at)sraoss(dot)co(dot)jp
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9849: walreceiver's DEBUG message reports wrong timestamp
Date: 2014-04-04 14:49:57
Message-ID: 6802.1396622997@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

harukat(at)sraoss(dot)co(dot)jp writes:
> We get the folloging message at the standby server.

> DEBUG: sendtime 2014-04-04 11:26:02.425368+09 receipttime 2014-04-04
> 11:26:02.425368+09 replication apply delay 0 ms transfer latency 224043 ms

> Though sendtime equals receipttime, transfer latency is large.
> This receipttime may be wrong.

Yeah, somebody forgot that timestamptz_to_str returns a static buffer.

strdupa is not a portable solution though.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Shahar 2014-04-04 19:14:37 Re: BUG #9833: daterange is not utilizing index correctly
Previous Message fburgess 2014-04-04 14:49:54 Re: Configuring Standby Server in PostgreSQL 9.3.3