Search PostgreSQL documentation
PG 18 · Browse by category, or enter a name or keyword
Category index4025
CompatibilityCompatibility
CREATE RULE is a PostgreSQL language extension, as is the entire query rewrite system.Compatibility
CompatibilityCompatibility
The SQL standard allows a DEFAULT CHARACTER SET clause in CREATE SCHEMA, as well as more subcommand types than are presently accepted by PostgreSQL.
The SQL standard specifies …Compatibility
CompatibilityCompatibility
CREATE SEQUENCE conforms to the SQL standard, with the following exceptions:
Obtaining the next value is done using the nextval() function instead of the standard's NEXT VALUE …Compatibility
CompatibilityCompatibility
CREATE SERVER conforms to ISO/IEC 9075-9 (SQL/MED).Compatibility
CompatibilityCompatibility
There is no CREATE STATISTICS command in the SQL standard.Compatibility
CompatibilityCompatibility
CREATE SUBSCRIPTION is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
The CREATE TABLE command conforms to the SQL standard, with exceptions listed below.Compatibility
CompatibilityCompatibility
CREATE TABLE AS conforms to the SQL standard. The following are nonstandard extensions:
The standard requires parentheses around the subquery clause; in PostgreSQL, these paren…Compatibility
CompatibilityCompatibility
CREATE TABLESPACE is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
This form of CREATE TRANSFORM is a PostgreSQL extension. There is a CREATE TRANSFORM command in the SQL standard, but it is for adapting data types to client languages. That us…Compatibility
CompatibilityCompatibility
The CREATE TRIGGER statement in PostgreSQL implements a subset of the SQL standard. The following functionalities are currently missing:
While transition table names for AFTER …Compatibility
CompatibilityCompatibility
There is no CREATE TEXT SEARCH CONFIGURATION statement in the SQL standard.Compatibility
CompatibilityCompatibility
There is no CREATE TEXT SEARCH DICTIONARY statement in the SQL standard.Compatibility
CompatibilityCompatibility
There is no CREATE TEXT SEARCH PARSER statement in the SQL standard.Compatibility
CompatibilityCompatibility
There is no CREATE TEXT SEARCH TEMPLATE statement in the SQL standard.Compatibility
CompatibilityCompatibility
The first form of the CREATE TYPE command, which creates a composite type, conforms to the SQL standard. The other forms are PostgreSQL extensions. The CREATE TYPE statement in…Compatibility
CompatibilityCompatibility
The CREATE USER statement is a PostgreSQL extension. The SQL standard leaves the definition of users to the implementation.Compatibility
CompatibilityCompatibility
CREATE USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED).Compatibility
CompatibilityCompatibility
CREATE OR REPLACE VIEW is a PostgreSQL language extension. So is the concept of a temporary view. The WITH ( ... ) clause is an extension as well, as are security barrier views…Compatibility
CompatibilityCompatibility
The SQL standard includes a DEALLOCATE statement, but it is only for use in embedded SQL.Compatibility
CompatibilityCompatibility
The SQL standard allows cursors only in embedded SQL and in modules. PostgreSQL permits cursors to be used interactively.
According to the SQL standard, changes made to insensi…Compatibility
CompatibilityCompatibility
This command conforms to the SQL standard, except that the USING and RETURNING clauses are PostgreSQL extensions, as is the ability to use WITH with DELETE.Compatibility
CompatibilityCompatibility
DISCARD is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
There is no DO statement in the SQL standard.Compatibility
CompatibilityCompatibility
DROP ACCESS METHOD is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
The DROP OWNED command is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
There is no DROP AGGREGATE statement in the SQL standard.Compatibility
CompatibilityCompatibility
The DROP CAST command conforms to the SQL standard.Compatibility
CompatibilityCompatibility
The DROP COLLATION command conforms to the SQL standard, apart from the IF EXISTS option, which is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
There is no DROP CONVERSION statement in the SQL standard, but a DROP TRANSLATION statement that goes along with the CREATE TRANSLATION statement that is similar to the CREATE …Compatibility
CompatibilityCompatibility
There is no DROP DATABASE statement in the SQL standard.Compatibility
CompatibilityCompatibility
This command conforms to the SQL standard, except for the IF EXISTS option, which is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
There is no DROP EVENT TRIGGER statement in the SQL standard.Compatibility
CompatibilityCompatibility
DROP EXTENSION is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
DROP FOREIGN DATA WRAPPER conforms to ISO/IEC 9075-9 (SQL/MED). The IF EXISTS clause is a PostgreSQL extension.Compatibility
CompatibilityCompatibility
This command conforms to ISO/IEC 9075-9 (SQL/MED), except that the standard only allows one foreign table to be dropped per command, and apart from the IF EXISTS option, which …Compatibility
CompatibilityCompatibility
This command conforms to the SQL standard, with these PostgreSQL extensions:
The standard only allows one function to be dropped per command. The IF EXISTS option The ability t…Compatibility
CompatibilityCompatibility
There is no DROP GROUP statement in the SQL standard.Compatibility
CompatibilityCompatibility
DROP INDEX is a PostgreSQL language extension. There are no provisions for indexes in the SQL standard.Compatibility
CompatibilityCompatibility
There is no DROP LANGUAGE statement in the SQL standard.Compatibility
More results
Find definitions in the PostgreSQL manuals, reference library, and extension catalogue.
pg17: choose a version ex: extensions only ↑↓ select ↵ open