| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence |
| Date: | 2019-10-01 05:41:54 |
| Message-ID: | 1893.1569908514@antos |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> wrote:
> The patch implementing new opclass option is attached.
>
> It adds new attribute pg_opclass.opcisbitwise, which is set to true if opclass
> equality is the same as binary equality.
> By default it is true.
I think the default value should be false and we should only set it to true
for individual opclasses which do meet the bitwise equality requirement. Also
extension authors should explicitly state that their data types are bitwise
equal. Otherwise the existing opclasses, when created via pg_dump ->
pg_restore, can be used by the system incorrectly.
> It is set to false for numeric and float4, float8.
Are you sure about these?
--
Antonin Houska
Web: https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-10-01 05:55:32 | Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence |
| Previous Message | Michael Paquier | 2019-10-01 05:06:00 | Re: recovery_min_apply_delay in archive recovery causes assertion failure in latch |