Search PostgreSQL documentation

CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard, except that the standard only allows one view to be dropped per command, and apart from the IF EXISTS option, which is a PostgreSQL e…Compatibility CompatibilityManual ChaptersPG18Compatibility END is a PostgreSQL extension that provides functionality equivalent to COMMIT, which is specified in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard includes an EXECUTE statement, but it is only for use in embedded SQL. This version of the EXECUTE statement also uses a somewhat different syntax.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no EXPLAIN statement defined in the SQL standard. The following syntax was used before PostgreSQL version 9.0 and is still supported: EXPLAIN [ ANALYZE ] [ VERBOSE ] s…Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard defines FETCH for use in embedded SQL only. The variant of FETCH described here returns the data as if it were a SELECT result rather than placing it in host v…Compatibility CompatibilityManual ChaptersPG18Compatibility According to the SQL standard, the PRIVILEGES key word in ALL PRIVILEGES is required. The SQL standard does not support setting the privileges on more than one object per comma…Compatibility CompatibilityManual ChaptersPG18Compatibility The IMPORT FOREIGN SCHEMA command conforms to the SQL standard, except that the OPTIONS clause is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility INSERT conforms to the SQL standard, except that the RETURNING clause is a PostgreSQL extension, as is the ability to use WITH with INSERT, and the ability to specify an altern…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no LISTEN statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility LOAD is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no LOCK TABLE in the SQL standard, which instead uses SET TRANSACTION to specify concurrency levels on transactions. PostgreSQL supports that too; see SET TRANSACTION …Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard. The WITH clause, BY SOURCE and BY TARGET qualifiers to WHEN NOT MATCHED, DO NOTHING action, and RETURNING clause are extensions to th…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no MOVE statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no NOTIFY statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility PREPARE TRANSACTION 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), bu…Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard includes a PREPARE statement, but it is only for use in embedded SQL. This version of the PREPARE statement also uses a somewhat different syntax.Compatibility CompatibilityManual ChaptersPG18Compatibility The REASSIGN OWNED command is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility REFRESH MATERIALIZED VIEW is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no REINDEX command in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard. The standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL allows it to be omitted.Compatibility CompatibilityManual ChaptersPG18Compatibility RESET is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility The compatibility notes of the GRANT command apply analogously to REVOKE. The keyword RESTRICT or CASCADE is required according to the standard, but PostgreSQL assumes RESTRICT…Compatibility CompatibilityManual ChaptersPG18Compatibility ROLLBACK 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 …Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard specifies that the key word SAVEPOINT is mandatory, but PostgreSQL and Oracle allow it to be omitted. SQL allows only WORK, not TRANSACTION, as a noise word af…Compatibility CompatibilityManual ChaptersPG18Compatibility The command ROLLBACK conforms to the SQL standard. The form ROLLBACK TRANSACTION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility SQL requires a savepoint to be destroyed automatically when another savepoint with the same name is established. In PostgreSQL, the old savepoint is kept, though only the more …Compatibility CompatibilityManual ChaptersPG18Compatibility There is no SECURITY LABEL command in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility Of course, the SELECT statement is compatible with the SQL standard. But there are some extensions and some missing features.Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard uses SELECT INTO to represent selecting values into scalar variables of a host program, rather than creating a new table. This indeed is the usage found in ECP…Compatibility CompatibilityManual ChaptersPG18Compatibility This command complies with the behavior defined in the SQL standard, except for the limitation that, in PostgreSQL, it does not apply to NOT NULL and CHECK constraints. Also, P…Compatibility CompatibilityManual ChaptersPG18Compatibility PostgreSQL allows identifier syntax ("rolename"), while the SQL standard requires the role name to be written as a string literal. SQL does not allow this command during a tran…Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard allows some other expressions to appear in place of the literal user_name, but these options are not important in practice. PostgreSQL allows identifier syntax…Compatibility CompatibilityManual ChaptersPG18Compatibility These commands are defined in the SQL standard, except for the DEFERRABLE transaction mode and the SET TRANSACTION SNAPSHOT form, which are PostgreSQL extensions. SERIALIZABLE …Compatibility CompatibilityManual ChaptersPG18Compatibility SET TIME ZONE extends syntax defined in the SQL standard. The standard allows only numeric time zone offsets while PostgreSQL allows more flexible time-zone specifications. All…Compatibility CompatibilityManual ChaptersPG18Compatibility The SHOW command is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility In the standard, it is not necessary to issue START TRANSACTION to start a transaction block: any SQL command implicitly begins a block. PostgreSQL's behavior can be seen as im…Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL:2008 standard includes a TRUNCATE command with the syntax TRUNCATE TABLE tablename. The clauses CONTINUE IDENTITY/RESTART IDENTITY also appear in that standard, but hav…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no UNLISTEN command in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard, except that the FROM and RETURNING clauses are PostgreSQL extensions, as is the ability to use WITH with UPDATE. Some other database …Compatibility CompatibilityManual ChaptersPG18Compatibility There is no VACUUM statement in the SQL standard. The following syntax was used before PostgreSQL version 9.0 and is still supported: VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ A…Compatibility