Re: Log timestamps at higher resolution

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Log timestamps at higher resolution
Date: 2018-10-25 01:10:20
Message-ID: 20181025011020.GB5902@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 25, 2018 at 01:00:08PM +1300, David Rowley wrote:
> On 25 October 2018 at 11:25, David Fetter <david(at)fetter(dot)org> wrote:
>> Strangely, there were no tests that came with that either. David, did
>> you mean to expand it past space padding, or...?
>
> Unsure what infrastructure existed then for testing this.

Close to none in-core for such things, the first set of TAP tests
included was 9.6, and at the time of 9.4 it was not even clear what we
were lookng for. You could have done things similar to what
test_decoding or pg_stat_statements are doing to enforce some
configuration parameters, but that would not have scaled with different
configurations. Another possibility would have been a buildfarm module.

Anyway, what has been done in this case looks fine to me with what was
present.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-10-25 01:12:52 Re: pgbench - add pseudo-random permutation function
Previous Message Michael Paquier 2018-10-25 00:47:51 Re: Function to promote standby servers