Horton

Re: [POC] hash partitioning

Jesper Pedersen <jesper.pedersen@redhat.com>

View thread View on postgr.es
From: Jesper Pedersen <jesper.pedersen@redhat.com>
To: amul sul <sulamul@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Thom Brown <thom@linux.com>, Robert Haas <robertmhaas@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Yugo Nagata <nagata@sraoss.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, David Steele <david@pgmasters.net>, Greg Stark <stark@mit.edu>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-10-06T12:05:51Z
Lists: pgsql-hackers 
Hi Amul,

On 09/28/2017 05:56 AM, amul sul wrote:
> It does not really do the partition pruning via constraint exclusion and I don't
> think anyone is going to use the remainder in the where condition to fetch
> data and hash partitioning is not meant for that.
> 
> But I am sure that we could solve this problem using your and Beena's work
> toward faster partition pruning[1] and Runtime Partition Pruning[2].
> 
> Will think on this changes if it is required for the pruning feature.
> 

Could you rebase on latest master ?

Best regards,
  Jesper

Commits

  1. Add hash partitioning.

  2. Add sanity check for pg_proc.provariadic

  3. Add hash_combine64.

  4. Make RelationGetPartitionDispatchInfo expand depth-first.

  5. Introduce 64-bit hash functions with a 64-bit seed.

  6. pg_dump: Add a --load-via-partition-root option.