[pgpool-general: 9109] Re: invalid memory alloc request size 18446744073709551593
Tatsuo Ishii
ishii at sraoss.co.jp
Fri May 31 00:46:06 JST 2024
> I'm using pgpool version 4.4.2 (nurikoboshi) and getting the following errors when pgpool starts. When I restart it again those errors no longer appear. It happens every 5-6 restarts that those errors appear.
>
> What might be causing this?
>
> 2024-05-30 17:16:07.953: pcp_main pid 22231: LOG: PCP process with pid: 24254 exit with SUCCESS.
> 2024-05-30 17:16:07.953: pcp_main pid 22231: LOG: PCP process with pid: 24254 exits with status 0
> 2024-05-30 17:16:24.180: main pid 22011: LOG: reaper handler
> 2024-05-30 17:16:24.181: main pid 22011: WARNING: child process with pid: 22193 was terminated by segmentation fault
> 2024-05-30 17:16:24.183: main pid 22011: LOG: reaper handler: exiting normally
> 2024-05-30 17:16:24.232: [unknown] pid 22165: ERROR: invalid memory alloc request size 18446744073709551593
> 2024-05-30 17:16:24.232: [unknown] pid 22165: CONTEXT: while searching system catalog, When relcache is missed
> 2024-05-30 17:16:24.266: [unknown] pid 22165: ERROR: invalid memory alloc request size 18446744073709551593
> 2024-05-30 17:16:24.267: [unknown] pid 22165: CONTEXT: while searching system catalog, When relcache is missed
> 2024-05-30 17:16:24.283: [unknown] pid 22165: ERROR: invalid memory alloc request size 18446744073709551593
> 2024-05-30 17:16:24.284: [unknown] pid 22165: CONTEXT: while searching system catalog, When relcache is missed
Looking at the place where the error occurred, I suspect this was
fixed by the commit after 4.4.2 is released:
https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=93f55858c6ba8b5243f5dc79808926961d78d826
So I recommend you to upgrade to 4.4.3 or higher because those
versions include the fix above.
Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
More information about the pgpool-general
mailing list