MIME-Version: 1.0
References: <be0339cc-1ae1-4892-9445-8e6d8995a44d@eisentraut.org>
 <47AEACEE-E5CC-40E4-8611-01F3A465AF16@yandex-team.ru> <9e7b21e7-4c63-4299-87f4-780a0699a7d8@eisentraut.org>
 <130996.1718814994@sss.pgh.pa.us> <CAMT0RQSdKQra6QC4b+eAynpqZ0SYdHDfGBBE7hty33OD9jx7Jg@mail.gmail.com>
 <647660.1719003075@sss.pgh.pa.us> <3110108.1719939353@sss.pgh.pa.us>
 <122E6623-E3B3-4945-9DF2-ADF86F7C63A7@yandex-team.ru> <2069996.1730557625@sss.pgh.pa.us>
In-Reply-To: <2069996.1730557625@sss.pgh.pa.us>
From: Hannu Krosing <hannuk@google.com>
Date: Sun, 3 Nov 2024 23:15:33 +0100
Message-ID: <CAMT0RQRNwvaHdH0hW+68BkW-b16jDzQXqjn2VM_Xk96ULhhSSg@mail.gmail.com>
Subject: Re: What is a typical precision of gettimeofday()?
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Peter Eisentraut <peter@eisentraut.org>, 
	pgsql-hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009589c50626098223"
Archived-At: <https://www.postgresql.org/message-id/CAMT0RQRNwvaHdH0hW%2B68BkW-b16jDzQXqjn2VM_Xk96ULhhSSg%40mail.gmail.com>
Precedence: bulk

--0000000000009589c50626098223
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Tom,

Did I understand correctly that you would prefer the documentation part to
be much smaller than it is now and all current the discussion about things
that are not strictly about the pg_test_timing to be not in the docs for it
?

My current plan is to move the other discussions around timing from th
edocs to PostgreSQL Wiki.

Would this be good ?

---
Best Regards
Hannu

On Sat, Nov 2, 2024 at 3:27=E2=80=AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "Andrey M. Borodin" <x4mmm@yandex-team.ru> writes:
> > This thread has associated CF entry which is marked as RwF [0]. But the
> change proved to be useful [1] in understanding what we can expect from
> time source.
> > It was requested many times before [2,3]. Reading through this thread i=
t
> seems to me that my questions about application of the pg_test_timing
> somehow switched focus from this patch. However, I'd appreciate if it was
> applied. Nanoseconds seem important to me.
> > Let me know if I can help in any way. Thanks!
>
> Basically, I think the code is ready, but I was awaiting Hannu's
> proposal on rewriting the documentation for pg_test_timing.
> Do you want to have a go at that?
>
>                         regards, tom lane
>

--0000000000009589c50626098223
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Tom,<br><br>Did I understand correctly that you would p=
refer the documentation part to be much smaller than it is now and all curr=
ent the discussion about things that are not strictly about the pg_test_tim=
ing to be not in the docs for it ?<br><br>My current plan is to move the ot=
her discussions around timing from th edocs to PostgreSQL Wiki.<br><br>Woul=
d this be good ?<br><br>---<br>Best Regards<br>Hannu</div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Nov 2, 2024 at =
3:27=E2=80=AFPM Tom Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.p=
gh.pa.us</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">&quot;Andrey M. Borodin&quot; &lt;<a href=3D"mailto:x4mmm@yandex-te=
am.ru" target=3D"_blank">x4mmm@yandex-team.ru</a>&gt; writes:<br>
&gt; This thread has associated CF entry which is marked as RwF [0]. But th=
e change proved to be useful [1] in understanding what we can expect from t=
ime source.<br>
&gt; It was requested many times before [2,3]. Reading through this thread =
it seems to me that my questions about application of the pg_test_timing so=
mehow switched focus from this patch. However, I&#39;d appreciate if it was=
 applied. Nanoseconds seem important to me.<br>
&gt; Let me know if I can help in any way. Thanks!<br>
<br>
Basically, I think the code is ready, but I was awaiting Hannu&#39;s<br>
proposal on rewriting the documentation for pg_test_timing.<br>
Do you want to have a go at that?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div>

--0000000000009589c50626098223--