Fix issues about namespace pg_ext_aux #340
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Namespace pg_ext_aux is different from the normal namespace created by the user. It's only used internally. The user isn't allowed to create table in pg_ext_aux explicitly.
For temp table, the namespace of the auxiliary table is also pg_ext_aux, not a temp namespace. It seems complicated to distinguish pg_ext_aux and pg_ext_aux_temp. The temp table will be automatically dropped when either the table is dropped or the session is closed. The internal auxiliary relation depends on the table will also automatically dropped if its table is dropped.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:
make installcheck
make -C src/test installcheck-cbdb-parallel
cloudberrydb/dev
team for review and approval when your PR is ready🥳