Yes.
UNIQUE
constraints are implemented using a unique B-tree index in Postgres.
See:
More Related Contents:
- How does PostgreSQL enforce the UNIQUE constraint / what type of index does it use?
- Postgresql: Conditionally unique constraint
- Do nullable columns occupy additional space in PostgreSQL?
- CONSTRAINT to check values from a remotely related table (via join etc.)
- PostgreSQL LIKE query performance variations
- Calculating and saving space in PostgreSQL
- Store common query as column?
- Making sense of Postgres row sizes
- Can PostgreSQL have a uniqueness constraint on array elements?
- Why does PostgreSQL perform sequential scan on indexed column?
- Does not using NULL in PostgreSQL still use a NULL bitmap in the header?
- How to add “on delete cascade” constraints?
- Grant all on a specific schema in the db to a group role in PostgreSQL
- Why can I create a table with PRIMARY KEY on a nullable column?
- Difference between GiST and GIN index
- Postgres query optimization (forcing an index scan)
- Postgres constraint for unique datetime range
- How does PostgreSQL perform ORDER BY with a b-tree index on the field?
- Optimize Postgres query on timestamp range
- Multicolumn index on 3 fields with heterogenous data types
- PostgreSQL – disabling constraints
- PostgreSQL Index on JSON
- Composite PRIMARY KEY enforces NOT NULL constraints on involved columns
- How to add a conditional unique index on PostgreSQL
- PostgreSQL – set a default cell value according to another cell value
- PostgreSQL composite primary key
- Insert, on duplicate update in PostgreSQL?
- How to convert a postgres database to sqlite
- SQL Sub queries in check constraint
- now() default values are all showing same timestamp