pg_dump/pg_dumpall do not dump storage servers or storage user mappings

Offen
#2,315 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c, postgresql, sql
Bereich
databases

Rechercherichtung

Start in src/bin/pg_dump/ and pg_dumpall, where the dump of roles and tablespaces is emitted, and check how --globals-only picks its objects. The catalogs to read are gp_storage_server and gp_storage_user_mapping. Done means the dump emits CREATE STORAGE SERVER and CREATE STORAGE USER MAPPING before per-database content, with the credential options handled like user-mapping options. Owner and comment output depends on #2312 landing first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Apache Cloudberry version

main (verified on a build of 3.0.0-devel)

What happened

Neither pg_dump nor pg_dumpall emits storage servers (gp_storage_server) or storage user mappings (gp_storage_user_mapping). There is no reference to either catalog anywhere under src/bin/pg_dump/.

As a result, a dump/restore (or any upgrade path that relies on pg_dumpall) silently loses every storage server definition, its options, and all storage user mappings. Directory tables that refer to those servers cannot work after the restore until the servers are recreated by hand.

This gap will also cover the properties added by #2312 (ALTER STORAGE SERVER ... OWNER TO and COMMENT ON STORAGE SERVER, for #1299). Neither a non-default owner nor a comment would survive a dump either.

What you think should happen instead

Because storage servers and their user mappings are cluster-wide (shared catalogs), pg_dumpall should emit them, as it does for roles and tablespaces:

  • CREATE STORAGE SERVER ... OPTIONS (...)
  • ALTER STORAGE SERVER ... OWNER TO ... (once #2312 lands)
  • COMMENT ON STORAGE SERVER ... IS ... (once #2312 lands)
  • CREATE STORAGE USER MAPPING FOR ... STORAGE SERVER ... OPTIONS (...)

They should be emitted before per-database content, so that directory tables restore against existing servers. Storage user mapping options may contain credentials, so they deserve the same consideration as user-mapping options in pg_dump. They should probably also be included in --globals-only.

How to reproduce
CREATE ROLE sm_owner;
CREATE STORAGE SERVER s1 OPTIONS (endpoint 'x');
CREATE STORAGE USER MAPPING FOR sm_owner STORAGE SERVER s1 OPTIONS (accesskey 'k');
pg_dumpall --globals-only | grep -ci 'storage server'   # 0
pg_dumpall | grep -i 'storage server'                   # nothing
Operating System

Rocky Linux 8 (also applies to any platform; the code is missing)

Anything else

Found while reviewing #2312.

Vorherrschende Sprache
C
Sterne
1.4k
Forks
273
Ø Merge
4 T. 6 Std.
Gemergte PRs (30 T.)
105

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudberry

Alle Issues in apache/cloudberry

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.