Search PostgreSQL documentation

CompatibilityManual ChaptersPG18Compatibility There is no ALTER TEXT SEARCH DICTIONARY statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no ALTER TEXT SEARCH PARSER statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no ALTER TEXT SEARCH TEMPLATE statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility The variants to add and drop attributes are part of the SQL standard; the other variants are PostgreSQL extensions.Compatibility CompatibilityManual ChaptersPG18Compatibility The ALTER USER statement is a PostgreSQL extension. The SQL standard leaves the definition of users to the implementation.Compatibility CompatibilityManual ChaptersPG18Compatibility ALTER USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). There is a subtle syntax issue: The standard omits the FOR key word. Since both CREATE USER MAPPING and DROP USER MAPPI…Compatibility CompatibilityManual ChaptersPG18Compatibility ALTER VIEW is a PostgreSQL extension of the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no ANALYZE statement in the SQL standard. The following syntax was used before PostgreSQL version 11 and is still supported: ANALYZE [ VERBOSE ] [ table_and_columns [,…Compatibility CompatibilityManual ChaptersPG18Compatibility BEGIN is a PostgreSQL language extension. It is equivalent to the SQL-standard command START TRANSACTION, whose reference page contains additional compatibility information. Th…Compatibility CompatibilityManual ChaptersPG18Compatibility CALL conforms to the SQL standard, except for the handling of output parameters. The standard says that users should write variables to receive the values of output parameters.Compatibility CompatibilityManual ChaptersPG18Compatibility The CHECKPOINT command is a PostgreSQL language extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CLOSE is fully conforming with the SQL standard. CLOSE ALL is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no CLUSTER statement in the SQL standard. The following syntax was used before PostgreSQL 17 and is still supported: CLUSTER [ VERBOSE ] [ table_name [ USING index_nam…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no COMMENT command in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility COMMIT PREPARED is a PostgreSQL extension. It is intended for use by external transaction management systems, some of which are covered by standards (such as X/Open XA), but th…Compatibility CompatibilityManual ChaptersPG18Compatibility The command COMMIT conforms to the SQL standard. The form COMMIT TRANSACTION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no COPY statement in the SQL standard. The following syntax was used before PostgreSQL version 9.0 and is still supported: COPY table_name [ ( column_name [, ...] ) ] …Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE ACCESS METHOD is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE AGGREGATE is a PostgreSQL language extension. The SQL standard does not provide for user-defined aggregate functions.Compatibility CompatibilityManual ChaptersPG18Compatibility The CREATE CAST command conforms to the SQL standard, except that SQL does not make provisions for binary-coercible types or extra arguments to implementation functions. AS IMP…Compatibility CompatibilityManual ChaptersPG18Compatibility There is a CREATE COLLATION statement in the SQL standard, but it is limited to copying an existing collation. The syntax to create a new collation is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE CONVERSION is a PostgreSQL extension. There is no CREATE CONVERSION statement in the SQL standard, but a CREATE TRANSLATION statement that is very similar in purpose and…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no CREATE DATABASE statement in the SQL standard. Databases are equivalent to catalogs, whose creation is implementation-defined.Compatibility CompatibilityManual ChaptersPG18Compatibility The command CREATE DOMAIN conforms to the SQL standard. The syntax NOT NULL in this command is a PostgreSQL extension. (A standard-conforming way to write the same for non-comp…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no CREATE EVENT TRIGGER statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE EXTENSION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE FOREIGN DATA WRAPPER conforms to ISO/IEC 9075-9 (SQL/MED), with the exception that the HANDLER and VALIDATOR clauses are extensions and the standard clauses LIBRARY and …Compatibility CompatibilityManual ChaptersPG18Compatibility The CREATE FOREIGN TABLE command largely conforms to the SQL standard; however, much as with CREATE TABLE, NULL constraints and zero-column foreign tables are permitted. The ab…Compatibility CompatibilityManual ChaptersPG18Compatibility A CREATE FUNCTION command is defined in the SQL standard. The PostgreSQL implementation can be used in a compatible way but has many extensions. Conversely, the SQL standard sp…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no CREATE GROUP statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE INDEX is a PostgreSQL language extension. There are no provisions for indexes in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE LANGUAGE is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE MATERIALIZED VIEW is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE OPERATOR CLASS is a PostgreSQL extension. There is no CREATE OPERATOR CLASS statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE OPERATOR is a PostgreSQL extension. There are no provisions for user-defined operators in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE OPERATOR FAMILY is a PostgreSQL extension. There is no CREATE OPERATOR FAMILY statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE POLICY is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility A CREATE PROCEDURE command is defined in the SQL standard. The PostgreSQL implementation can be used in a compatible way but has many extensions. For details see also CREATE FU…Compatibility CompatibilityManual ChaptersPG18Compatibility CREATE PUBLICATION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility The CREATE ROLE statement is in the SQL standard, but the standard only requires the syntax CREATE ROLE name [ WITH ADMIN role_name ] Multiple initial administrators, and all t…Compatibility