Re: incorrect handling of the timeout in pg_receivexlog - Mailing list pgsql-hackers

From Tom Lane
Subject Re: incorrect handling of the timeout in pg_receivexlog
Date
Msg-id 6616.1328626514@sss.pgh.pa.us
Whole thread Raw
In response to Re: incorrect handling of the timeout in pg_receivexlog  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: incorrect handling of the timeout in pg_receivexlog  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> On 07.02.2012 09:03, Fujii Masao wrote:
>> What about changing receivelog.c so that it uses time_t instead of
>> TimestampTz? Which would make the code simpler, I think.

> Hmm, that would reduce granularity to seconds.

It also creates portability issues that I'd just as soon not deal with,
ie, time_t is not the same width on all platforms.  (The integer vs
float TimestampTz issue is a kind of portability problem, but we've
already bought into the assumption that sender and receiver must be
built with the same choice, no?)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Marko Kreen
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage
Next
From: Tom Lane
Date:
Subject: Re: Removing special case OID generation