pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Using WaitEventSet in the postmaster
Date: Thu, 12 Jan 2023 01:27:16 -0500
Message-ID: <901504.1673504836@sss.pgh.pa.us> (raw )
In-Reply-To: <CA+hUKGK-gv8=_0FPe3MMZkncozmTNBRT7NhsKBt3vHZ5Dxu2=A@mail.gmail.com >
References: <20221205180939.2p6zcrtevukgyay7@awork3.anarazel.de >
<CA+hUKGLU6t-17dywkMADMBdPHhfvnHaS2JzWbu2Fd80220hrpw@mail.gmail.com >
<20221206231230.3vwxd5dfc3gkf4vl@awork3.anarazel.de >
<CA+hUKGLw+QFMpzTs4t84vUWQM-LWkv0Q67BVk0vBGvkpdUC7Yg@mail.gmail.com >
<20221207012224.hjcyzvwdjim22e2a@awork3.anarazel.de >
<CA+hUKGLAHAuHPJ9oWaRHP-CoME9MuATW=afZ+WQXHXMNw2m7rg@mail.gmail.com >
<CA+hUKGJa+7=KccV+YJD9KtmOxyXmToxSRuTaAVvh14rNFh8LjQ@mail.gmail.com >
<CA+hUKGKt58vOw8Y32Cy_Lnj8K2FGrty6-XO+bmkRnyuz5w-wJw@mail.gmail.com >
<20230106232512.46jdujlcknqgj2ct@awork3.anarazel.de >
<CA+hUKGLPZ8NUPfwAfi6Gd0y4CRSzBCTeAy7irE2B=-YsxAO3fQ@mail.gmail.com >
<20230107225548.ppzg4rpninlthgth@awork3.anarazel.de >
<CA+hUKGLGcUoFLDAMPEoU2EP-UmdGs+tHcfusxbyav71wgMrzLg@mail.gmail.com >
<CA+hUKGK-gv8=_0FPe3MMZkncozmTNBRT7NhsKBt3vHZ5Dxu2=A@mail.gmail.com >
Thomas Munro <thomas.munro@gmail.com> writes:
> Pushed, after a few very minor adjustments, mostly comments. Thanks
> for the reviews and pointers. I think there are quite a lot of
> refactoring and refinement opportunities unlocked by this change (I
> have some draft proposals already), but for now I'll keep an eye on
> the build farm.
skink seems to have found a problem:
==2011873== VALGRINDERROR-BEGIN
==2011873== Syscall param epoll_wait(events) points to unaddressable byte(s)
==2011873== at 0x4D8DC73: epoll_wait (epoll_wait.c:30)
==2011873== by 0x55CA49: WaitEventSetWaitBlock (latch.c:1527)
==2011873== by 0x55D591: WaitEventSetWait (latch.c:1473)
==2011873== by 0x4F2B28: ServerLoop (postmaster.c:1729)
==2011873== by 0x4F3E85: PostmasterMain (postmaster.c:1452)
==2011873== by 0x42643C: main (main.c:200)
==2011873== Address 0x7b1e620 is 1,360 bytes inside a recently re-allocated block of size 8,192 alloc'd
==2011873== at 0x48407B4: malloc (vg_replace_malloc.c:381)
==2011873== by 0x6D9D30: AllocSetContextCreateInternal (aset.c:446)
==2011873== by 0x4F2D9B: PostmasterMain (postmaster.c:614)
==2011873== by 0x42643C: main (main.c:200)
==2011873==
==2011873== VALGRINDERROR-END
regards, tom lane
view thread (28+ messages) latest in thread
Message-ID: <901504.1673504836@sss.pgh.pa.us>
Permalink: ../901504.1673504836@sss.pgh.pa.us/
Also on: postgresql.org/message-id/901504.1673504836@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, andres@anarazel.de
Subject: Re: Using WaitEventSet in the postmaster
In-Reply-To: <901504.1673504836@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox