Also on your location clause you should not reference the same file more
than one time.
If you want to scale gpfdist process you need to use different range on
each port for a same server. (Not sure if I explain myself :))
If you use one gpfdist per server performance should be fine. One gpfdist
Your default_hash_table_bucket_number value is set to 6. Typically, this
should be adjusted as 6 x #_of_your_segment_hosts. With 3 segments, you
should set this value to 18. Any time you change this parameter, you should
redistribute your HASH distributed tables, if you have any (unless the
table
My environment is : 1 master 3 segments
SQL >>:
CREATE TABLE call_center (
cc_call_center_sk integer,
cc_call_center_id character varying(16),
cc_rec_start_date date,
cc_rec_end_date date,
cc_closed_date_sk integer,
cc_open_date_sk integer,
cc_name character
Could you please post your SQL DDL statement? How many URLs do you have in
your external table? Also, your HASH dist table - how many buckets are
defined, if any? Are the # of URLs more than the # of buckets or
default_hash_table_bucket_number value? Perhaps you can attach your
hawq-site.xml file
