Skip to content

Conversation

@lss602726449
Copy link
Contributor

Fixes #ISSUE_Number

What does this PR do?

Type of Change

  • Bug fix (non-breaking change)
  • New feature (non-breaking change)
  • Breaking change (fix or feature with breaking changes)
  • Documentation update

Breaking Changes

Test Plan

  • Unit tests added/updated
  • Integration tests added/updated
  • Passed make installcheck
  • Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

Additional Context

CI Skip Instructions


bmdoil and others added 2 commits November 27, 2025 10:56
This commit drops the GPDB specific TypeStorageOptions
struct and supporting code in favor of adding
pg_type_encoding.typoptions to the getTypes query.

The usage of CatalogId as the hash index caused collisions
with the TypeInfo indexes when TypeStorageOptions was a
unique dumpable object, since the only unique aspect was the
typstorage field. Now, when dumpType is called, we check the
typstorage field and dump the ALTER TABLE...SET DEFAULT ENCODING
TOC entry if needed.

Authored-by: Brent Doil <[email protected]>
@my-ship-it my-ship-it changed the title [Draft]Fix pg_upgrade and pg_dump [WIP]Fix pg_upgrade and pg_dump Nov 28, 2025
1. Add database type and version to pg_upgrade and pg_dump to
distinguish different catalogs.
2. Fixed serveral issues encountered when using pg_dump and pg_upgrade.
@lss602726449 lss602726449 changed the title [WIP]Fix pg_upgrade and pg_dump Fix pg_upgrade and pg_dump Nov 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants