Re: parallel plan in insert query
От | Amit Kapila |
---|---|
Тема | Re: parallel plan in insert query |
Дата | |
Msg-id | CAA4eK1JFyx+Q9HBb_dB0_sQh=P7xeLJDOi8rxEdzNiPV4c-bPA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: parallel plan in insert query (Grigory Smolkin <g.smolkin@postgrespro.ru>) |
Список | pgsql-bugs |
On Tue, Oct 11, 2016 at 5:18 PM, Grigory Smolkin <g.smolkin@postgrespro.ru> wrote: > It`s INSERT: > 2016-10-07 19:41:41 MSK [11404]: [78416-1] > user=gis,db=gis,app=psql,client=[local] STATEMENT: > explain analyze insert into edges_snapped_speeds select gid, speed*3600, ts > from (select * from traffic_snapped_tracks limit 2) a join lateral > snaptopgr(geom) on true; > > It does qualify query as 'write query'? > That's right, but parallelism can be used read part of query. For example, insert into t1 select * from parallel_exec(); Now if there is some statement in parallel_exec() function, that can use parallelism. Example function definition which can use parallelism: create or replace function parallel_exec() returns integer as $$ begin Perform * from t1 where c1 >= 10 and c1 < 11; return 1; end; $$ language plpgsql STABLE PARALLEL SAFE; -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-bugs по дате отправления: