Re: [HACKERS] [POC] hash partitioning - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] [POC] hash partitioning
Date
Msg-id CA+Tgmoa-6z2kw_W6GP_-0jFOWu-3PVnyS4gC6-s=sPH4w0bhqg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [POC] hash partitioning  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] [POC] hash partitioning
List pgsql-hackers
On Thu, Oct 12, 2017 at 4:20 PM, Andres Freund <andres@anarazel.de> wrote:
>> In other words, it's not utterly fixed in stone --- we invented
>> --load-via-partition-root primarily to cope with circumstances that
>> could change hash values --- but we sure don't want to be changing it
>> with any regularity, or for a less-than-excellent reason.
>
> Yea, that's what I expected. It'd probably good for somebody to run
> smhasher or such on the output of the combine function (or even better,
> on both the 32 and 64 bit variants) in that case.

Not sure how that test suite works exactly, but presumably the
characteristics in practice will depend the behavior of the hash
functions used as input the combine function - so the behavior could
be good for an (int, int) key but bad for a (text, date) key, or
whatever.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Pluggable storage
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] [POC] hash partitioning