Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Date
Msg-id 20220617.155926.1280463387721038464.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
At Fri, 17 Jun 2022 15:54:13 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> > Or we could add a timeout.c API that specifies the timeout?
> 
> I sometimes wanted this, But I don't see a simple way to sort multiple
> relative timeouts in absolute time order.  Maybe we can skip
> GetCurrentTimestamp only when inserting the first timeout, but I don't
> think it benefits this case.

Or we can use a free-run interval timer and individual down-counter
for each timtouts.  I think we need at-most 0.1s resolution and error
of long-run timer doesn't harm?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Next
From: Peter Eisentraut
Date:
Subject: Re: Typo in ro.po file?