<para>

The formal name of the SQL standard is ISO/IEC 9075 <quote>Database

Language SQL</quote>. A revised version of the standard is released

from time to time; the most recent update appearing in2011.

The2011 version is referred to as ISO/IEC 9075:2011, or simply as SQL:2011.

The versions prior to that were SQL:2008, SQL:2006, SQL:2003, SQL:1999,

and SQL-92. Each version

from time to time; the most recent update appearing in2016.

The2016 version is referred to as ISO/IEC 9075:2016, or simply as SQL:2016.

The versions prior to that were SQL:2011, SQL:2008, SQL:2006, SQL:2003,

SQL:1999,and SQL-92. Each version

replaces the previous one, so claims of conformance to earlier

versions have no official merit.

<productname>PostgreSQL</productname> development aims for

</para>

<para>

PostgreSQL supports most of the major features of SQL:2011. Out of

PostgreSQL supports most of the major features of SQL:2016. Out of

179 mandatory features required for full Core conformance,

PostgreSQL conforms to at least 160. In addition, there is a long

list of supported optional features. It might be worth noting that at

the time of writing, no current version of any database management

system claims full conformance to Core SQL:2011.

system claims full conformance to Core SQL:2016.

</para>

<para>

In the following two sections, we provide a list of those features

that <productname>PostgreSQL</productname> supports, followed by a

list of the features defined in <acronym>SQL:2011</acronym> which

list of the features defined in <acronym>SQL:2016</acronym> which

are not yet supported in <productname>PostgreSQL</productname>.

Both of these lists are approximate: There might be minor details that

are nonconforming for a feature that is listed as supported, and

<title>Unsupported Features</title>

<para>

The following features defined in <acronym>SQL:2011</acronym> are not

The following features defined in <acronym>SQL:2016</acronym> are not

implemented in this release of

<productname>PostgreSQL</productname>. In a few cases, equivalent

functionality is available.

INSERT INTO sql_partsVALUES ('10','Object Language Bindings (SQL/OLB)','NO',NULL,'');

INSERT INTO sql_partsVALUES ('11','Information and Definition Schema (SQL/Schemata)','NO',NULL,'');

INSERT INTO sql_partsVALUES ('13','Routines and Types Using the Java Programming Language (SQL/JRT)','NO',NULL,'');

INSERT INTO sql_partsVALUES ('14','XML-Related Specifications (SQL/XML)','YES',NULL,'');

INSERT INTO sql_partsVALUES ('14','XML-Related Specifications (SQL/XML)','NO',NULL,'');

B126Routine language PascalNO

B127Routine language PL/INO

B128Routine language SQLNO

B200Polymorphic table functionsNO

B201More than one PTF generic table parameterNO

B202PTF CopartitioningNO

B203More than one copartition specificationNO

B204PRUNE WHEN EMPTYNO

B205Pass-through columnsNO

B206PTF descriptor parametersNO

B207Cross products of partitioningsNO

B208PTF component procedure interfaceNO

B209PTF extended namesNO

B211Module language Ada: VARCHAR and NUMERIC supportNO

B221Routine language Ada: VARCHAR and NUMERIC supportNO

E011Numeric data typesYES

F401Extended joined table04CROSS JOINYES

F402Named column joins for LOBs, arrays, and multisetsYES

F403Partitioned joined tablesNO

F404Range variable for common column namesNO

F411Time zone specificationYESdifferences regarding literal interpretation

F421National characterYES

F431Read-only scrollable cursorsYES

F661Simple tablesYES

F671Subqueries in CHECKNOintentionally omitted

F672Retrospective check constraintsYES

F673Reads SQL-data routine invocations in CHECK constraintsNO

F690Collation supportYESbut no character set support

F692Extended collation supportYES

F693SQL-session and client module collationsNO

F865<offset row count> in <result offset clause>YES

F866FETCH FIRST clause: PERCENT optionNO

F867FETCH FIRST clause: WITH TIES optionNO

R010Row pattern recognition: FROM clauseNO

R020Row pattern recognition: WINDOW clauseNO

R030Row pattern recognition: full aggregate supportNO

S011Distinct data typesNO

S011Distinct data types01USER_DEFINED_TYPES viewNO

S023Basic structured typesNO

T043Multiplier TNO

T044Multiplier PNO

T051Row typesNO

T052MAX and MIN for row typesNO

T053Explicit aliases for all-fields referenceNO

T061UCS supportNO

T071BIGINT data typeYES

T076DECFLOAT data typeNO

T101Enhanced nullability determinationNO

T111Updatable joins, unions, and columnsNO

T121WITH (excluding RECURSIVE) in query expressionYES

T511Transaction countsNO

T521Named arguments in CALL statementYES

T522Default values for IN parameters of SQL-invoked proceduresNOsupported except DEFAULT key word in invocation

T523Default values for INOUT parameters of SQL-invoked proceduresYES

T524Named arguments in routine invocations other than a CALL statementYES

T525Default values for parameters of SQL-invoked functionsYES

T551Optional key words for default syntaxYES

T561Holdable locatorsNO

T571Array-returning external SQL-invoked functionsNO

T619Nested window functionsNO

T620WINDOW clause: GROUPS optionYES

T621Enhanced numeric functionsYES

T622Trigonometric functionsYES

T623General logarithm functionsYES

T624Common logarithm functionsYES

T625LISTAGGNO

T631IN predicate with one list elementYES

T641Multiple column assignmentNOonly some syntax variants supported

T651SQL-schema statements in SQL routinesYES

T652SQL-dynamic statements in SQL routinesNO

T653SQL-schema statements in external routinesNO

T654SQL-dynamic statements in external routinesNO

T655Cyclically dependent routinesYES

T811Basic SQL/JSON constructor functionsNO

T812SQL/JSON: JSON_OBJECTAGGNO

T813SQL/JSON: JSON_ARRAYAGG with ORDER BYNO

T814Colon in JSON_OBJECT or JSON_OBJECTAGGNO

T821Basic SQL/JSON query operatorsNO

T822SQL/JSON: IS JSON WITH UNIQUE KEYS predicateNO

T823SQL/JSON: PASSING clauseNO

T824JSON_TABLE: specific PLAN clauseNO

T825SQL/JSON: ON EMPTY and ON ERROR clausesNO

T826General value expression in ON ERROR or ON EMPTY clausesNO

T827JSON_TABLE: sibling NESTED COLUMNS clausesNO

T828JSON_QUERYNO

T829JSON_QUERY: array wrapper optionsNO

T830Enforcing unique keys in SQL/JSON constructor functionsNO

T831SQL/JSON path language: strict modeNO

T832SQL/JSON path language: item methodNO

T833SQL/JSON path language: multiple subscriptsNO

T834SQL/JSON path language: wildcard member accessorNO

T835SQL/JSON path language: filter expressionsNO

T836SQL/JSON path language: starts with predicateNO

T837SQL/JSON path language: regex_like predicateNO

T838JSON_TABLE: PLAN DEFAULT clauseNO

T839Formatted cast of datetimes to/from character stringsNO

M001DatalinksNO

M002Datalinks via SQL/CLINO

M003Datalinks via Embedded SQLNO