Re: parse partition strategy string in gram.y - Mailing list pgsql-hackers

From Finnerty, Jim
Subject Re: parse partition strategy string in gram.y
Date
Msg-id B2B74C3C-9998-4AF9-805B-9F37E946F3B9@amazon.com
Whole thread Raw
In response to Re: parse partition strategy string in gram.y  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parse partition strategy string in gram.y  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Or if you know the frequencies of the highly frequent values of the partitioning key at the time the partition bounds
aredefined, you could define hash ranges that contain approximately the same number of rows in each partition.  A
parallelsequential scan of all partitions would then perform better because data skew is minimized. 
 


pgsql-hackers by date:

Previous
From: Reid Thompson
Date:
Subject: Re: Add the ability to limit the amount of memory that can be allocated to backends.
Next
From: Reid Thompson
Date:
Subject: Re: Add tracking of backend memory allocated to pg_stat_activity