The CFP is now open & will close on Feb 9, 2025! The 4th annual event called POSETTE: An Event for Postgres will happen Jun 10-12, 2025 and the Call for Speakers is now open—unt ...

PGConf.dev 2025]( (May 13-16, 2025, Montreal, CA), aka [PostgreSQL Development Conference 2025]( is an event where users, developers, and community ...

We're pleased to announce that we published the schedule of the PGDay/MED 2024 taking place in Naples, Italy, on December ...

If you have pattern matching needs that go beyond this, consider writing a user-defined function in Perl or Tcl. While most regular-expression searches can be executed very quickly, regular ...

PostgreSQL provides various lock modes to control concurrent access to data in tables. These modes can be used for application-controlled locking in situations where MVCC does not give the desired ...

CREATE INDEX constructs an index on the specified column(s) of the specified table. Indexes are primarily used to enhance database performance (though inappropriate use can result in slower ...

ALTER LARGE OBJECT — change the definition of a large object ALTER MATERIALIZED VIEW — change the definition of a materialized view ALTER OPERATOR — change the definition of an operator ALTER OPERATOR ...

postmaster.opts A file recording the command-line options the server was last started with postmaster.pid A lock file recording the current postmaster process ID (PID), cluster data directory path, ...

pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore ...

CREATE TABLE will create a new, initially empty table in the current database. The table will be owned by the user issuing the command. If a schema name is given (for example, CREATE TABLE ...

This section describes the detailed format of each message. Each is marked to indicate that it can be sent by a frontend (F), a backend (B), or both (F & B). Notice that although each message includes ...

#> text[] Get JSON object at specified path '{"a": {"b":{"c": "foo"}}}'::json#>'{a,b}' {"c": "foo"} @> jsonb Does the left JSON value contain the right JSON path ...