From 2fc2a88e6722df40245d3ae2ec7f8fc1c6bf0596 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 25 Oct 2019 21:11:48 +0200 Subject: Remove obsolete information schema tables Remove SQL_LANGUAGES, which was eliminated in SQL:2008, and SQL_PACKAGES and SQL_SIZING_PROFILES, which were eliminated in SQL:2011. Since they were dropped by the SQL standard, the information in them was no longer updated and therefore no longer useful. This also removes the feature-package association information in sql_feature_packages.txt, but for the time begin we are keeping the information which features are in the Core package (that is, mandatory SQL features). Maybe at some point someone wants to invent a way to store that that does not involve using the "package" mechanism anymore. Discussion https://www.postgresql.org/message-id/flat/91334220-7900-071b-9327-0c6ecd012017%402ndquadrant.com --- doc/src/sgml/features.sgml | 9 +- doc/src/sgml/information_schema.sgml | 216 ----------------------------------- 2 files changed, 3 insertions(+), 222 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml index f767bee46e5..2c5a7e5d0c5 100644 --- a/doc/src/sgml/features.sgml +++ b/doc/src/sgml/features.sgml @@ -44,10 +44,7 @@ broad three levels found in SQL-92. A large subset of these features represents the Core features, which every conforming SQL implementation must supply. - The rest of the features are purely optional. Some optional - features are grouped together to form packages, which - SQL implementations can claim conformance to, thus claiming - conformance to particular groups of features. + The rest of the features are purely optional. @@ -116,7 +113,7 @@ Identifier - Package + Core? Description Comment @@ -143,7 +140,7 @@ Identifier - Package + Core? Description Comment diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 906fe7819f5..7a995a1b649 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -4963,160 +4963,6 @@ ORDER BY c.ordinal_position; - - <literal>sql_languages</literal> - - - The table sql_languages contains one row for - each SQL language binding that is supported by - PostgreSQL. - PostgreSQL supports direct SQL and - embedded SQL in C; that is all you will learn from this table. - - - - This table was removed from the SQL standard in SQL:2008, so there - are no entries referring to standards later than SQL:2003. - - - - <literal>sql_languages</literal> Columns - - - - - Name - Data Type - Description - - - - - - sql_language_source - character_data - - The name of the source of the language definition; always - ISO 9075, that is, the SQL standard - - - - - sql_language_year - character_data - - The year the standard referenced in - sql_language_source was approved. - - - - - sql_language_conformance - character_data - - The standard conformance level for the language binding. For - ISO 9075:2003 this is always CORE. - - - - - sql_language_integrity - character_data - Always null (This value is relevant to an earlier version of the SQL standard.) - - - - sql_language_implementation - character_data - Always null - - - - sql_language_binding_style - character_data - - The language binding style, either DIRECT or - EMBEDDED - - - - - sql_language_programming_language - character_data - - The programming language, if the binding style is - EMBEDDED, else null. PostgreSQL only - supports the language C. - - - - -
- - - - <literal>sql_packages</literal> - - - The table sql_packages contains information - about which feature packages defined in the SQL standard are - supported by PostgreSQL. Refer to for background information on feature packages. - - - - <literal>sql_packages</literal> Columns - - - - - Name - Data Type - Description - - - - - - feature_id - character_data - Identifier string of the package - - - - feature_name - character_data - Descriptive name of the package - - - - is_supported - yes_or_no - - YES if the package is fully supported by the - current version of PostgreSQL, NO if not - - - - - is_verified_by - character_data - - Always null, since the PostgreSQL development group does not - perform formal testing of feature conformance - - - - - comments - character_data - Possibly a comment about the supported status of the package - - - -
- - <literal>sql_parts</literal> @@ -5239,68 +5085,6 @@ ORDER BY c.ordinal_position; - - <literal>sql_sizing_profiles</literal> - - - The table sql_sizing_profiles contains - information about the sql_sizing values that are - required by various profiles of the SQL standard. PostgreSQL does - not track any SQL profiles, so this table is empty. - - - - <literal>sql_sizing_profiles</literal> Columns - - - - - Name - Data Type - Description - - - - - - sizing_id - cardinal_number - Identifier of the sizing item - - - - sizing_name - character_data - Descriptive name of the sizing item - - - - profile_id - character_data - Identifier string of a profile - - - - required_value - cardinal_number - - The value required by the SQL profile for the sizing item, or 0 - if the profile places no limit on the sizing item, or null if - the profile does not require any of the features for which the - sizing item is applicable - - - - - comments - character_data - Possibly a comment pertaining to the sizing item within the profile - - - -
- - <literal>table_constraints</literal> -- cgit v1.2.3