From: | Robert Haas <rhaas(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Update pg_stat_statements extension for parallel query. |
Date: | 2016-06-10 15:01:25 |
Message-ID: | E1bBNw5-0008EQ-HN@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Update pg_stat_statements extension for parallel query.
All functions provided by this extension are PARALLEL SAFE. Given the
general prohibition against write operations in parallel queries, it is
perhaps a bit surprising that pg_stat_statements_reset() is parallel safe.
But since it only modifies shared memory, not the database, it's OK.
Andreas Karlsson
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/496899ccc2fd1b84bd1a8c8b3a7f0c667e5329f0
Modified Files
--------------
contrib/pg_stat_statements/Makefile | 6 +--
.../pg_stat_statements--1.3--1.4.sql | 7 ++++
.../pg_stat_statements/pg_stat_statements--1.3.sql | 48 ----------------------
.../pg_stat_statements/pg_stat_statements--1.4.sql | 48 ++++++++++++++++++++++
.../pg_stat_statements/pg_stat_statements.control | 2 +-
5 files changed, 59 insertions(+), 52 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-06-10 15:26:23 | Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
Previous Message | Tom Lane | 2016-06-10 14:50:36 | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-10 15:12:46 | Re: Hard to maintain duplication in contain_volatile_functions_not_nextval_walker |
Previous Message | Tom Lane | 2016-06-10 14:50:36 | Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted |