On 2022-05-13 22:09, Andres Freund wrote:
What does
sysctl kern.timecounter
return? Does the problem continue if you switch kern.timecounter.hardware to
something else?
openbsd 5.9:
$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hard
Hi,
On 2022-05-13 10:22:32 -0700, Andres Freund wrote:
> On 2022-05-13 09:00:20 +0200, Mikael Kjellström wrote:
> > Well, I don't know if you remember but there was a thread a while back and a
> > test program (monotime.c) to test the clock if it could go backwards and
> > openbsd showed the follo
Hi,
On 2022-05-13 09:00:20 +0200, Mikael Kjellström wrote:
> Well, I don't know if you remember but there was a thread a while back and a
> test program (monotime.c) to test the clock if it could go backwards and
> openbsd showed the following result when running the attached testprogram:
Nope, d
On 2022-05-13 04:14, Andres Freund wrote:
One interesting tidbit is that the log timestamps are computed differently
(with elog.c:get_formatted_log_time()) than the reset timestamp (with
GetCurrentTimestamp()). Both use gettimeofday() internally.
I wonder if there's a chance that somehow open
Hi,
On 2022-05-12 19:14:13 -0700, Andres Freund wrote:
> On 2022-05-12 21:42:43 -0400, Melanie Plageman wrote:
> > Andres drew my attention to this [1] build farm failure.
I just saw that there's another recent timestamp related failure:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=go
Hi,
On 2022-05-12 21:42:43 -0400, Melanie Plageman wrote:
> Andres drew my attention to this [1] build farm failure.
>
> Looks like a test I wrote resetting pg_stat_replication_slots is
> failing:
>
> # Failed test 'Check that reset timestamp is later after resetting
> stats for slot 'test_s
On Fri, May 13, 2022 at 12:01:09PM +1000, Peter Smith wrote:
> I don't know if this is related, but I noticed that the log timestamp
> (19:59:58.342) is reporting the $reset1 value (19:59:58.402808).
>
> I did not understand how a timestamp saved from the past could be
> ahead of the timestamp of
On Fri, May 13, 2022 at 11:43 AM Melanie Plageman
wrote:
>
> Andres drew my attention to this [1] build farm failure.
>
> Looks like a test I wrote resetting pg_stat_replication_slots is
> failing:
>
> # Failed test 'Check that reset timestamp is later after resetting
> stats for slot 'test_sl
Andres drew my attention to this [1] build farm failure.
Looks like a test I wrote resetting pg_stat_replication_slots is
failing:
# Failed test 'Check that reset timestamp is later after resetting
stats for slot 'test_slot' again.'
# at t/006_logical_decoding.pl line 261.
# go
