Rearrange extension-related views as per recent discussion.
The original design of pg_available_extensions did not consider the possibility of version-specific control files. Split it into two views: pg_available_extensions shows information that is generic about an extension, while pg_available_extension_versions shows all available versions together with information that could be version-dependent. Also, add an SRF pg_extension_update_paths() to assist in checking that a collection of update scripts provide sane update path sequences.
Showing
- doc/src/sgml/catalogs.sgml 82 additions, 8 deletionsdoc/src/sgml/catalogs.sgml
- doc/src/sgml/extend.sgml 14 additions, 0 deletionsdoc/src/sgml/extend.sgml
- src/backend/catalog/system_views.sql 10 additions, 4 deletionssrc/backend/catalog/system_views.sql
- src/backend/commands/extension.c 391 additions, 18 deletionssrc/backend/commands/extension.c
- src/bin/psql/tab-complete.c 1 addition, 1 deletionsrc/bin/psql/tab-complete.c
- src/include/catalog/catversion.h 1 addition, 1 deletionsrc/include/catalog/catversion.h
- src/include/catalog/pg_proc.h 6 additions, 2 deletionssrc/include/catalog/pg_proc.h
- src/include/utils/builtins.h 2 additions, 0 deletionssrc/include/utils/builtins.h
- src/test/regress/expected/rules.out 63 additions, 62 deletionssrc/test/regress/expected/rules.out
Loading
Please register or sign in to comment