Re: Automatically sizing the IO worker pool - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Automatically sizing the IO worker pool
Date
Msg-id CA+hUKG+wbaZZ9Nwc_bTopm4f-7vDmCwLk80uKDHj9mq+Up0E+g@mail.gmail.com
Whole thread Raw
In response to Re: Automatically sizing the IO worker pool  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
BTW I would like to push 0001 and 0002 to master/18.  They are are not
behaviour changes, they just fix up a bunch of inconsistent (0001) and
misleading (0002) variable naming and comments to reflect reality (in
AIO v1 the postmaster used to assign those I/O worker numbers, now the
postmaster has its own array of slots to track them that is *not*
aligned with the ID numbers/slots in shared memory ie those numbers
you see in the ps status, so that's bound to confuse people
maintaining this code).  I just happened to notice that when working
on this dynamic worker pool stuff.  If there are no objections I will
go ahead and do that soon.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Avoiding memory leak when compilation of a function fails
Next
From: Michael Paquier
Date:
Subject: Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl