On 5 October 2018 at 09:43, Harry B wrote:
> Now the big question: How scared should I be relying on this? I don't mind
> it breaking on major version upgrades (which would mean I need to dump &
> restore my entire set), but how likely is it to change unannounced in a
> minor/security release? Unl
Thanks for the quick response David! this has been really helpful.
Looking at the code, this step wasn't totally unnecessary - if I had
multi-column hash you would have had to do this step anyways - because pg
hashes each column separately and combines them. True, unnecessary for
single column has
On 5 October 2018 at 06:18, Harry B wrote:
>
> Thank you David! These helped me create an operator class.
> However, there still seems to be a 'off-by-a-fixed-N' difference between the
> hash value returned and how PG selects the partition.
hmm, actually, this is probably due to the hash_combine6
Thank you David! These helped me create an operator class.
However, there still seems to be a 'off-by-a-fixed-N' difference between
the hash value returned and how PG selects the partition.
http://dpaste.com/381E6CF
Am I overlooking some endianness difference!!??
For this setup, values are alway
On 4 October 2018 at 16:22, Harry B wrote:
> I am still having trouble reconciling what happens under the HASH
> partitioning!. If I have text column forming the basis of PARTITIONED BY
> HASH, the HASH value used in the partitioning setup does not seem to match
> to `hashtext()` of that value
It
Hi,
I am still having trouble reconciling what happens under the HASH
partitioning!. If I have text column forming the basis of PARTITIONED BY
HASH, the HASH value used in the partitioning setup does not seem to match
to `hashtext()` of that value
CREATE TABLE loopy (k TEXT PRIMARY KEY, something
Hi,
Since I didn't hear back on how to make partitioning work using a custom
hash function, I ended up changing my app/client to use postgres' built-in
hash method instead - I just needed them to match.
https://github.com/harikb/pghash
https://github.com/harikb/pghash/blob/master/lib/pghash/pghas
Hi,
I am interested in trying the hash partitioning method now available in 11
(trying the beta 4). However, I have the data already hashed at the
application level across multiple postgres instances. If possible, I would
like to keep these two hashing methods same. This would enable me to move
a
