Re: PG10 Crash-safe and replicable Hash Indexes and UNIQUE

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG10 Crash-safe and replicable Hash Indexes and UNIQUE
Date: 2017-05-22 22:39:18
Message-ID: 20170522223918.taugpuqfsa4o745n@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Chapman Flack wrote:

> That was what gave me the idea in the first place, which then
> I realized could be more generally useful. If I could say
> something like
>
> CREATE INDEX ON foo USING btree ( bar, baz ALSO quux );
>
> so that only bar and baz are compared in insertion and search,
> but quux is along for the ride and available to index-only scans,

INCLUDING:
https://www.postgresql.org/message-id/56168952.4010101@postgrespro.ru

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neha Khatri 2017-05-22 23:08:12 Improve logical decoding error message (was wal_level > WAL_LEVEL_LOGICAL)
Previous Message Jeff Janes 2017-05-22 22:08:35 ALTER PUBLICATION materializing the list of tables