pgsql/doc/src/sgml/html/information-schema.html - master - Ao/MaxReport

pgsql/doc/src/sgml/html/information-schema.html
31 строка13 KB
AoAnima
first_commit
13 июл 2026, 17:47
13 июл 2026, 17:47f1a670a
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type … [Строка слишком длинная. Вы можете скачать файл]
  The information schema consists of a set of views that contain
  information about the objects defined in the current database.  The
  information schema is defined in the SQL standard and can therefore
  be expected to be portable and remain stable — unlike the system
  catalogs, which are specific to
  <span class="productname">PostgreSQL</span> and are modeled after
  implementation concerns.  The information schema views do not,
  however, contain information about
  <span class="productname">PostgreSQL</span>-specific features; to inquire
  about those you need to query the system catalogs or other
  <span class="productname">PostgreSQL</span>-specific views.
 </p><div class="note"><h3 class="title">Note</h3><p>
   When querying the database for constraint information, it is possible
   for a standard-compliant query that expects to return one row to
   return several.  This is because the SQL standard requires constraint
   names to be unique within a schema, but
   <span class="productname">PostgreSQL</span> does not enforce this
   restriction.  <span class="productname">PostgreSQL</span>
   automatically-generated constraint names avoid duplicates in the
   same schema, but users can specify such duplicate names.
  </p><p>
   This problem can appear when querying information schema views such
   as <code class="literal">check_constraint_routine_usage</code>,
   <code class="literal">check_constraints</code>, <code class="literal">domain_constraints</code>, and
   <code class="literal">referential_constraints</code>.  Some other views have similar
   issues but contain the table name to help distinguish duplicate
   rows, e.g., <code class="literal">constraint_column_usage</code>,
   <code class="literal">constraint_table_usage</code>, <code class="literal">table_constraints</code>.
  </p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ecpg-sql-whenever.html" title="WHENEVER">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="client-interfaces.html" title="Part IV. Client Interfaces">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="infoschema-schema.html" title="35.1. The Schema">Next</a></td></tr><tr><td width="40%" align="left" valign="top">WHENEVER </td><td width="20%" align="center"><a accesskey="h" href="index.html" title="PostgreSQL 18.4 Documentation">Home</a></td><td width="40%" align="right" valign="top"> 35.1. The Schema</td></tr></table></div></body></html>