diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/parallel.sgml | 16 |
1 files changed, 4 insertions, 12 deletions
diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml index 2a25f21eb4b..1f5efd9e6d9 100644 --- a/doc/src/sgml/parallel.sgml +++ b/doc/src/sgml/parallel.sgml @@ -151,9 +151,10 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; <para> The query writes any data or locks any database rows. If a query contains a data-modifying operation either at the top level or within - a CTE, no parallel plans for that query will be generated. This is a - limitation of the current implementation which could be lifted in a - future release. + a CTE, no parallel plans for that query will be generated. As an + exception, the commands <literal>CREATE TABLE</>, <literal>SELECT + INTO</>, and <literal>CREATE MATERIALIZED VIEW</> which create a new + table and populate it can use a parallel plan. </para> </listitem> @@ -243,15 +244,6 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; <listitem> <para> - A prepared statement is executed using a <literal>CREATE TABLE .. AS - EXECUTE ..</literal> statement. This construct converts what otherwise - would have been a read-only operation into a read-write operation, - making it ineligible for parallel query. - </para> - </listitem> - - <listitem> - <para> The transaction isolation level is serializable. This situation does not normally arise, because parallel query plans are not generated when the transaction isolation level is serializable. |