Re: Refactoring postmaster's code to cleanup after child exit
| От | Alexander Lakhin |
|---|---|
| Тема | Re: Refactoring postmaster's code to cleanup after child exit |
| Дата | |
| Msg-id | 451b0797-83b8-cdbc-727f-8d7a7b0e3bca@gmail.com обсуждение |
| Ответ на | Re: Refactoring postmaster's code to cleanup after child exit (Heikki Linnakangas <hlinnaka@iki.fi>) |
| Ответы |
Re: Refactoring postmaster's code to cleanup after child exit
|
| Список | pgsql-hackers |
Hello Heikki,
10.08.2024 00:13, Heikki Linnakangas wrote:
>
> Committed the patches up to and including this one, with tiny comment changes.
I've noticed that on the current HEAD server.log contains binary data
(an invalid process name) after a child crash. For example, while playing
with -ftapv, I've got:
SELECT to_date('2024 613566758 1', 'IYYY IW ID');
server closed the connection unexpectedly
grep -a 'was terminated' server.log
2024-08-18 07:07:06.482 UTC|||66c19d96.3482f6|LOG: `�!x� (PID 3441407) was terminated by signal 6: Aborted
It looks like this was introduced by commit 28a520c0b (IIUC, namebuf in
CleanupBackend() may stay uninitialized in some code paths).
Best regards,
Alexander
В списке pgsql-hackers по дате отправления: