Databases
StackOverflow2013
Postsdbo
POGreenplum data distribution among segments
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGreenplum data distribution among segments
    primarykey
    data
    text
    <p>I have a Greenplum database, in which I have 10 segments reflecting the 10 hard disks. My table is divided into primary partition based on date and secondary partition based on hash id. So for a month there will be 30 primary partition and each partition containing 100 sub partition. And the data in the sub-partition is loaded based on hashid. Now the question is how these partitions are distributed among the segments.</p> <p>Guess 1:</p> <pre><code>seg1(equally distributed based on pri partition : 30datepartition/10=3 date partitions) date1---0-99 sub partition of hashid date2---0-99 sub partition of hashid date3---0-99 sub partition of hashid seg2(equally contains 30/10=3 date partitions) date4---0-99 partition of hashid date5---0-99 partition of hashid date6---0-99 partition of hashid ... .. seg10 date27---0-99 partition of hashid date28---0-99 partition of hashid date29---0-99 partition of hashid </code></pre> <p>OR</p> <p>Guess 2</p> <pre><code>seg1(distributed by 100hashid/10=10 hashid partitions) date1---0-9 partition of hashid date2---0-9 partition of hashid ... date30---0-9 partition of hashid seg2(equally contains 100hashid/10=10 hashid partitions) date1---10-19 partition of hashid date2---10-19 partition of hashid ... date30---10-19 partition of hashid </code></pre> <p>How does this work? Guess 1 or 2, if both are wrong kindly en light me on the way it is distributed on segment level.</p> <p>Is it a good design to sub-partition it based on hash id. As I am dealing with 6 million records every day, and i have to store date for a year, i wanted the search to hit on very less portion of data. In other words based on the key query i will determine and hashid range and it will search in those specific partitions. </p> <p>Thanks Ganesh.R</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USYang
    1. USGanesh R
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGreenplum data distribution among segments
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGreenplum data distribution among segments
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload