database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00
Code Activity

Remove obsolete information schema tables

Browse Source 
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
This commit is contained in:
Peter Eisentraut
2019-10-25 21:11:48 +02:00
parent 592a16321b
commit 2fc2a88e67
7 changed files with 4 additions and 329 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/features.sgml
View File

@ -44,10 +44,7 @@
broad three levels found in <acronym>SQL-92</acronym>. A large
subset of these features represents the <quote>Core</quote>
features, which every conforming SQL implementation must supply.
The rest of the features are purely optional. Some optional
features are grouped together to form <quote>packages</quote>, which
SQL implementations can claim conformance to, thus claiming
conformance to particular groups of features.
The rest of the features are purely optional.
</para>
<para>
@ -116,7 +113,7 @@
<thead>
<row>
<entry>Identifier</entry>
<entry>Package</entry>
<entry>Core?</entry>
<entry>Description</entry>
<entry>Comment</entry>
</row>
@ -143,7 +140,7 @@
<thead>
<row>
<entry>Identifier</entry>
<entry>Package</entry>
<entry>Core?</entry>
<entry>Description</entry>
<entry>Comment</entry>
</row>

216
doc/src/sgml/information_schema.sgml
View File

@ -4963,160 +4963,6 @@ ORDER BY c.ordinal_position;
</table>
</sect1>
<sect1 id="infoschema-sql-languages">
<title><literal>sql_languages</literal></title>
<para>
The table <literal>sql_languages</literal> contains one row for
each SQL language binding that is supported by
<productname>PostgreSQL</productname>.
<productname>PostgreSQL</productname> supports direct SQL and
embedded SQL in C; that is all you will learn from this table.
</para>
<para>
This table was removed from the SQL standard in SQL:2008, so there
are no entries referring to standards later than SQL:2003.
</para>
<table>
<title><literal>sql_languages</literal> Columns</title>
<tgroup cols="3">
<thead>
<row>
<entry>Name</entry>
<entry>Data Type</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>sql_language_source</literal></entry>
<entry><type>character_data</type></entry>
<entry>
The name of the source of the language definition; always
<literal>ISO 9075</literal>, that is, the SQL standard
</entry>
</row>
<row>
<entry><literal>sql_language_year</literal></entry>
<entry><type>character_data</type></entry>
<entry>
The year the standard referenced in
<literal>sql_language_source</literal> was approved.
</entry>
</row>
<row>
<entry><literal>sql_language_conformance</literal></entry>
<entry><type>character_data</type></entry>
<entry>
The standard conformance level for the language binding. For
ISO 9075:2003 this is always <literal>CORE</literal>.
</entry>
</row>
<row>
<entry><literal>sql_language_integrity</literal></entry>
<entry><type>character_data</type></entry>
<entry>Always null (This value is relevant to an earlier version of the SQL standard.)</entry>
</row>
<row>
<entry><literal>sql_language_implementation</literal></entry>
<entry><type>character_data</type></entry>
<entry>Always null</entry>
</row>
<row>
<entry><literal>sql_language_binding_style</literal></entry>
<entry><type>character_data</type></entry>
<entry>
The language binding style, either <literal>DIRECT</literal> or
<literal>EMBEDDED</literal>
</entry>
</row>
<row>
<entry><literal>sql_language_programming_language</literal></entry>
<entry><type>character_data</type></entry>
<entry>
The programming language, if the binding style is
<literal>EMBEDDED</literal>, else null. <productname>PostgreSQL</productname> only
supports the language C.
</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="infoschema-sql-packages">
<title><literal>sql_packages</literal></title>
<para>
The table <literal>sql_packages</literal> contains information
about which feature packages defined in the SQL standard are
supported by <productname>PostgreSQL</productname>. Refer to <xref
linkend="features"/> for background information on feature packages.
</para>
<table>
<title><literal>sql_packages</literal> Columns</title>
<tgroup cols="3">
<thead>
<row>
<entry>Name</entry>
<entry>Data Type</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>feature_id</literal></entry>
<entry><type>character_data</type></entry>
<entry>Identifier string of the package</entry>
</row>
<row>
<entry><literal>feature_name</literal></entry>
<entry><type>character_data</type></entry>
<entry>Descriptive name of the package</entry>
</row>
<row>
<entry><literal>is_supported</literal></entry>
<entry><type>yes_or_no</type></entry>
<entry>
<literal>YES</literal> if the package is fully supported by the
current version of <productname>PostgreSQL</productname>, <literal>NO</literal> if not
</entry>
</row>
<row>
<entry><literal>is_verified_by</literal></entry>
<entry><type>character_data</type></entry>
<entry>
Always null, since the <productname>PostgreSQL</productname> development group does not
perform formal testing of feature conformance
</entry>
</row>
<row>
<entry><literal>comments</literal></entry>
<entry><type>character_data</type></entry>
<entry>Possibly a comment about the supported status of the package</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="infoschema-sql-parts">
<title><literal>sql_parts</literal></title>
@ -5239,68 +5085,6 @@ ORDER BY c.ordinal_position;
</table>
</sect1>
<sect1 id="infoschema-sql-sizing-profiles">
<title><literal>sql_sizing_profiles</literal></title>
<para>
The table <literal>sql_sizing_profiles</literal> contains
information about the <literal>sql_sizing</literal> values that are
required by various profiles of the SQL standard. <productname>PostgreSQL</productname> does
not track any SQL profiles, so this table is empty.
</para>
<table>
<title><literal>sql_sizing_profiles</literal> Columns</title>
<tgroup cols="3">
<thead>
<row>
<entry>Name</entry>
<entry>Data Type</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>sizing_id</literal></entry>
<entry><type>cardinal_number</type></entry>
<entry>Identifier of the sizing item</entry>
</row>
<row>
<entry><literal>sizing_name</literal></entry>
<entry><type>character_data</type></entry>
<entry>Descriptive name of the sizing item</entry>
</row>
<row>
<entry><literal>profile_id</literal></entry>
<entry><type>character_data</type></entry>
<entry>Identifier string of a profile</entry>
</row>
<row>
<entry><literal>required_value</literal></entry>
<entry><type>cardinal_number</type></entry>
<entry>
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
</entry>
</row>
<row>
<entry><literal>comments</literal></entry>
<entry><type>character_data</type></entry>
<entry>Possibly a comment pertaining to the sizing item within the profile</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="infoschema-table-constraints">
<title><literal>table_constraints</literal></title>