Re: Refactoring postmaster's code to cleanup after child exit
Heikki Linnakangas <hlinnaka@iki.fi>
Attachments
- v5-0001-Add-test-for-connection-limits.patch (text/x-patch) patch v5-0001
- v5-0002-Add-test-for-dead-end-backends.patch (text/x-patch) patch v5-0002
On 06/09/2024 12:52, Heikki Linnakangas wrote: > Unless you have comments on these first two patches which just add > tests, I'll commit them shortly. Still processing the rest of your > comments... Didn't happen as "shortly" as I thought.. My test for dead-end backends opens 20 TCP (or unix domain) connections to the server, in quick succession. That works fine my system, and it passed cirrus CI on other platforms, but on FreeBSD it failed repeatedly. The behavior in that scenario is apparently platform-dependent: it depends on the accept queue size, but what happens when you reach the queue size also seems to depend on the platform. On my Linux system, the connect() calls in the client are blocked, if the server is doesn't call accept() fast enough, but apparently you get an error on *BSD systems. I'm not sure of the exact details, but in any case, platform-dependent behavior needs to be avoided in tests. So I changed the test so that it sends an SSLRequest packet on each connection and waits for reply (which is always 'N' to reject it in this test), before opening the next connection. This way, each connection is still left hanging, which is what I want in this test, but only after postmaster has successfully accept()ed it and forked the backend. So here are these test patches again, with that addition. -- Heikki Linnakangas Neon (https://neon.tech)
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix test name and username used in failed connection attempts
- 2a943afcff44 18.0 landed
-
tests: Don't fail due to high default timeout in postmaster/003_start_stop
- b48832cddbf5 18.0 landed
-
tests: Fix race condition in postmaster/002_connection_limits
- 71d1ed6fe129 18.0 landed
-
Pass MyPMChildSlot as an explicit argument to child process
- 5b007868577a 18.0 landed
-
Assign a child slot to every postmaster child process
- a78af0427015 18.0 landed
-
Kill dead-end children when there's nothing else left
- bb861414fea3 18.0 landed
-
Replace postmaster.c's own backend type codes with BackendType
- 18d67a8d7d30 18.0 landed
-
Use an shmem_exit callback to remove backend from PMChildFlags on exit
- 2bbc261ddbdf 18.0 landed
-
Add test for dead-end backends
- 85ec945b7880 18.0 landed
-
Add test for connection limits
- 6a1d0d470e84 18.0 landed
-
Fix garbled process name on backend crash
- 56d23855c864 18.0 landed
-
Consolidate postmaster code to launch background processes
- 3354f85284dc 18.0 landed
-
Fix comment on processes being kept over a restart
- a79ed10e6c6b 18.0 landed
-
Refactor code to handle death of a backend or bgworker in postmaster
- 28a520c0b773 18.0 landed
-
Make BackgroundWorkerList doubly-linked
- b43100fa71d7 18.0 landed
-
Minor refactoring of assign_backendlist_entry()
- 63bef4df975c 18.0 landed
-
Fix outdated comment; all running bgworkers are in BackendList
- ef4c35b4166e 18.0 landed
-
Allow building with MSVC and Strawberry perl
- 341f4e002d46 16.0 cited
-
Fix rare failure in LDAP tests.
- f44b9b625bed 14.0 cited
-
Allow notifications to bgworkers without database connections.
- 8a02b3d732cf 9.6.0 cited