Hi Zweistein,
I'm checking internally on this; I suspect the answer is "no, no concerns" as it's specifically about pg_dump having a race condition that can be exploited, but will get a confirmation.
However, that being said it looks like it's fixed in PGSQL 15.8, which is supported (15.x is supported). So should be no harm is simply upgrading the Postgres instance to 15.8 where the issue is resolved.
I'm checking internally on this; I suspect the answer is "no, no concerns" as it's specifically about pg_dump having a race condition that can be exploited, but will get a confirmation.
However, that being said it looks like it's fixed in PGSQL 15.8, which is supported (15.x is supported). So should be no harm is simply upgrading the Postgres instance to 15.8 where the issue is resolved.
Statistics: Posted by david.domask — Aug 12, 2024 2:43 pm
