This was an actual bug only apparent when testing on different cluster timezone configurations. I have fixed it and drafted a new release 1.5.2. Thanks for all your help with this. I hope this one passes! It does on my own machine and the VM I spun up on which I was able to reproduce your test failure.
Thanks,
On Wed, Nov 28, 2018 at 10:08 AM Jeremy Finzel <finzelj@gmail.com> wrote:
Dear Christoph,
Thank you for the full log. I can't reproduce this issue on several machines ... is it possible for you to run this with log_min_messages = DEBUG and log_min_duration_statement = 0 and provide output?
Thanks,
On Wed, Nov 28, 2018 at 8:44 AM Christoph Berg <myon@debian.org> wrote: