postgres/pg_stat_statements.control at 356f85f95cb0b0e99ce51932c2a9dbd292f0b292 - postgres - GitFox

database/postgres

mirror of https://github.com/postgres/postgres.git synced 2025-08-14 02:22:38 +03:00

Files

config

contrib

adminpack

auth_delay

auto_explain

bloom

btree_gin

btree_gist

chkpass

citext

cube

dblink

dict_int

dict_xsyn

earthdistance

file_fdw

fuzzystrmatch

hstore

hstore_plperl

hstore_plpython

intagg

intarray

isn

lo

ltree

ltree_plpython

oid2name

pageinspect

passwordcheck

pg_buffercache

pg_freespacemap

pg_prewarm

pg_standby

pg_stat_statements

Makefile

pg_stat_statements--1.0--1.1.sql

pg_stat_statements--1.1--1.2.sql

pg_stat_statements--1.2--1.3.sql

pg_stat_statements--1.3--1.4.sql

pg_stat_statements--1.4.sql

pg_stat_statements--unpackaged--1.0.sql

pg_stat_statements.c

pg_stat_statements.control

pg_trgm

pg_visibility

pgcrypto

pgrowlocks

pgstattuple

postgres_fdw

seg

sepgsql

spi

sslinfo

start-scripts

tablefunc

tcn

test_decoding

tsearch2

tsm_system_rows

tsm_system_time

unaccent

uuid-ossp

vacuumlo

xml2

Makefile

README

contrib-global.mk

doc

src

.dir-locals.el

.gitattributes

.gitignore

COPYRIGHT

GNUmakefile.in

HISTORY

Makefile

README

README.git

aclocal.m4

configure

configure.in

Robert Haas 496899ccc2 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

2016-06-10 10:42:01 -04:00

6 lines

191 B

Plaintext

Raw Blame History

 # pg_stat_statements extension
 comment = 'track execution statistics of all SQL statements executed'
 default_version = '1.4'
 module_pathname = '$libdir/pg_stat_statements'
 relocatable = true