From: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: parallel plan in insert query |
Date: | 2016-10-11 11:48:19 |
Message-ID: | a5193373-f255-322e-415a-84d92d562843@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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'?
On 10/11/2016 02:41 PM, Greg Stark wrote:
> The query doesn't look like a write query from the sql or the plan you
> sent. My guess is that one of the PostGIS
> functions does an update or insert internally. It should probably be
> marked VOLATILE in that case which I'm not sure but would assume would
> disable parallel queries as well. But there are reasons why they might
> not want to do that too in which case this is the kind of risk that
> would come with.
>
>
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-10-11 12:24:41 | Re: parallel plan in insert query |
Previous Message | Greg Stark | 2016-10-11 11:41:44 | Re: parallel plan in insert query |