Hello,
On Wed, Jul 31, 2019 at 10:55 AM Evgeny Efimkin <efimkin(at)yandex-team(dot)ru> wrote:
>
> What reason to use pg_atomic_uint64?
The queryid is read and written without holding any lock on the PGPROC
entry, so the pg_atomic_uint64 will guarantee that we get a consistent
value in pg_stat_get_activity(). Other reads shouldn't be a problem
as far as I remember.
> In docs:
> occured - > occurred
Thanks! I fixed it on my local branch.