Postpone calls of unsafe server-side functions in pg_dump. Avoid calling pg_get_partkeydef(), pg_get_expr(relpartbound), and regtypeout until we have lock on the relevant tables. The existing coding is at serious risk of failure if there are any concurrent DROP TABLE commands going on --- including drops of other sessions' temp tables. Back-patch of commit e3fcbbd62. That's been in v15/HEAD long enough to have some confidence about it, so now let's fix the problem in older branches. Original patch by me; thanks to Gilles Darold for back-patching legwork. Discussion: https://postgr.es/m/[email protected] Discussion: https://postgr.es/m/[email protected] Discussion: https://postgr.es/m/[email protected] Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b1f106420b1a1703a1703fdf90bcdd703f322cd1 Modified Files -------------- src/bin/pg_dump/pg_dump.c | 166 +++++++++++++++++++++++++--------------------- src/bin/pg_dump/pg_dump.h | 4 +- 2 files changed, 93 insertions(+), 77 deletions(-)
pgsql-committers by date:
Соглашаюсь с условиями обработки персональных данных
