| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Юрий Соколов <funny(dot)falcon(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index. |
| Date: | 2020-02-20 20:59:43 |
| Message-ID: | CAH2-Wz=_wt8D4v-1=MfhvWiyevrk+esWgE51tTnBpsOVDwN9Kw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 20, 2020 at 10:58 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I think that there is a good chance that it just won't matter. The
> number of indexes that won't be able to support deduplication will be
> very small in practice. The important exceptions are INCLUDE indexes
> and nondeterministic collations. These exceptions make sense
> intuitively, and will be documented as limitations of those other
> features.
I wasn't clear about the implication of what I was saying here, which
is: I will make the NOTICE a DEBUG1 message, and leave everything else
as-is in the initial committed version.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-20 22:05:14 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
| Previous Message | Thomas Munro | 2020-02-20 20:50:29 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |