Search PostgreSQL documentation

CompatibilityManual ChaptersPG18Compatibility DROP MATERIALIZED VIEW is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP OPERATOR CLASS statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP OPERATOR statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP OPERATOR FAMILY statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility DROP POLICY is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard, with these PostgreSQL extensions: The standard only allows one procedure to be dropped per command. The IF EXISTS option is an extens…Compatibility CompatibilityManual ChaptersPG18Compatibility DROP PUBLICATION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility The SQL standard defines DROP ROLE, but it allows only one role to be dropped at a time, and it specifies different privilege requirements than PostgreSQL uses.Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard, with these PostgreSQL extensions: The standard only allows one routine to be dropped per command. The IF EXISTS option is an extensio…Compatibility CompatibilityManual ChaptersPG18Compatibility DROP RULE is a PostgreSQL language extension, as is the entire query rewrite system.Compatibility CompatibilityManual ChaptersPG18Compatibility DROP SCHEMA is fully conforming with the SQL standard, except that the standard only allows one schema to be dropped per command, and apart from the IF EXISTS option, which is …Compatibility CompatibilityManual ChaptersPG18Compatibility DROP SEQUENCE conforms to the SQL standard, except that the standard only allows one sequence to be dropped per command, and apart from the IF EXISTS option, which is a Postgre…Compatibility CompatibilityManual ChaptersPG18Compatibility DROP SERVER conforms to ISO/IEC 9075-9 (SQL/MED). The IF EXISTS clause is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP STATISTICS command in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility DROP SUBSCRIPTION is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility This command conforms to the SQL standard, except that the standard only allows one table to be dropped per command, and apart from the IF EXISTS option, which is a PostgreSQL …Compatibility CompatibilityManual ChaptersPG18Compatibility DROP TABLESPACE is a PostgreSQL extension.Compatibility CompatibilityManual ChaptersPG18Compatibility This form of DROP TRANSFORM is a PostgreSQL extension. See CREATE TRANSFORM for details.Compatibility CompatibilityManual ChaptersPG18Compatibility The DROP TRIGGER statement in PostgreSQL is incompatible with the SQL standard. In the SQL standard, trigger names are not local to tables, so the command is simply DROP TRIGGE…Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP TEXT SEARCH CONFIGURATION statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP TEXT SEARCH DICTIONARY statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP TEXT SEARCH PARSER statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility There is no DROP TEXT SEARCH TEMPLATE statement in the SQL standard.Compatibility CompatibilityManual ChaptersPG18Compatibility This command is similar to the corresponding command in the SQL standard, apart from the IF EXISTS option, which is a PostgreSQL extension. But note that much of the CREATE TYP…Compatibility CompatibilityManual ChaptersPG18Compatibility The DROP USER statement is a PostgreSQL extension. The SQL standard leaves the definition of users to the implementation.Compatibility CompatibilityManual ChaptersPG18Compatibility DROP USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). The IF EXISTS clause is a PostgreSQL extension.Compatibility 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