Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date
Msg-id 5CDFBA04-DEBC-4BFD-BDC0-42CA1828AAD0@yesql.se
Whole thread Raw
In response to Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications  (Georgy Artos <georgyartos@gmail.com>)
List pgsql-bugs
> On 4 Feb 2025, at 15:43, Georgy Artos <georgyartos@gmail.com> wrote:

> Post Scriptum: There's a non-namespaced/schematized query at [4],
> however I guess it's really just me not understanding the pg_dump
> code...

> [4]
https://github.com/postgres/postgres/blob/53a49365052026907afff7613929710d1e7f0da0/src/bin/pg_dump/pg_dump.c#L1723C18-L1723C32

Thanks for the report, any such query should be fixed.  In this case it seems
fine, partition_tree is set up as a recursive common table expression a few
lines earlier in the function:

  if (with_child_tables)
  {
      appendPQExpBuffer(query, "WITH RECURSIVE partition_tree (relid) AS (\n");
  }

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: Georgy Artos
Date:
Subject: Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Next
From: Laurenz Albe
Date:
Subject: Re: BUG #18793: PLpgSQL Function Returning Type of Table is not match for varchar(n) data type via Return Query