From: Pavan D. <pav...@gm...> - 2013-07-04 08:43:18
|
On Thu, Jul 4, 2013 at 2:10 PM, 鈴木 幸市 <ko...@in...> wrote: > We've cleaned up some function I/F and it may influenced the case. > > Any more info? > It seems we are trying to FQS this query, which is clearly wrong. The INSERTs must go through the coordinator so that each row can be inserted in the relevant datanode. If I turn FQS off, then the INSERT works fine. postgres=# set enable_fast_query_shipping TO on; SET postgres=# EXPLAIN INSERT INTO testtbl VALUES (generate_series(1,10000), 'foo'); QUERY PLAN ---------------------------------------------------------------------------- Data Node Scan on "__REMOTE_FQS_QUERY__" (cost=0.00..0.00 rows=0 width=0) Node expr: generate_series(1, 10000) (2 rows) postgres=# set enable_fast_query_shipping TO off; SET postgres=# EXPLAIN INSERT INTO testtbl VALUES (generate_series(1,10000), 'foo'); QUERY PLAN ----------------------------------------------------- Insert on testtbl (cost=0.00..0.01 rows=1 width=0) Node/s: d1, d2 Node expr: a -> Result (cost=0.00..0.01 rows=1 width=0) (4 rows) Thanks, Pavan -- Pavan Deolasee http://www.linkedin.com/in/pavandeolasee |