2010-09-20 22:08:53 +02:00
|
|
|
# contrib/pg_stat_statements/Makefile
|
2009-01-04 23:19:59 +01:00
|
|
|
|
|
|
|
MODULE_big = pg_stat_statements
|
2019-11-05 23:41:07 +01:00
|
|
|
OBJS = \
|
|
|
|
$(WIN32RES) \
|
|
|
|
pg_stat_statements.o
|
2009-01-04 23:19:59 +01:00
|
|
|
|
2011-02-14 02:06:41 +01:00
|
|
|
EXTENSION = pg_stat_statements
|
2022-04-08 06:12:07 +02:00
|
|
|
DATA = pg_stat_statements--1.4.sql \
|
|
|
|
pg_stat_statements--1.9--1.10.sql pg_stat_statements--1.8--1.9.sql \
|
Allow pg_stat_statements to track planning statistics.
This commit makes pg_stat_statements support new GUC
pg_stat_statements.track_planning. If this option is enabled,
pg_stat_statements tracks the planning statistics of the statements,
e.g., the number of times the statement was planned, the total time
spent planning the statement, etc. This feature is useful to check
the statements that it takes a long time to plan. Previously since
pg_stat_statements tracked only the execution statistics, we could
not use that for the purpose.
The planning and execution statistics are stored at the end of
each phase separately. So there are not always one-to-one relationship
between them. For example, if the statement is successfully planned
but fails in the execution phase, only its planning statistics are stored.
This may cause the users to be able to see different pg_stat_statements
results from the previous version. To avoid this,
pg_stat_statements.track_planning needs to be disabled.
This commit bumps the version of pg_stat_statements to 1.8
since it changes the definition of pg_stat_statements function.
Author: Julien Rouhaud, Pascal Legrand, Thomas Munro, Fujii Masao
Reviewed-by: Sergei Kornilov, Tomas Vondra, Yoshikazu Imai, Haribabu Kommi, Tom Lane
Discussion: https://postgr.es/m/CAHGQGwFx_=DO-Gu-MfPW3VQ4qC7TfVdH2zHmvZfrGv6fQ3D-Tw@mail.gmail.com
Discussion: https://postgr.es/m/CAEepm=0e59Y_6Q_YXYCTHZkqOc6H2pJ54C_Xe=VFu50Aqqp_sA@mail.gmail.com
Discussion: https://postgr.es/m/DB6PR0301MB21352F6210E3B11934B0DCC790B00@DB6PR0301MB2135.eurprd03.prod.outlook.com
2020-04-02 04:20:19 +02:00
|
|
|
pg_stat_statements--1.7--1.8.sql pg_stat_statements--1.6--1.7.sql \
|
2019-01-11 04:20:09 +01:00
|
|
|
pg_stat_statements--1.5--1.6.sql pg_stat_statements--1.4--1.5.sql \
|
|
|
|
pg_stat_statements--1.3--1.4.sql pg_stat_statements--1.2--1.3.sql \
|
2020-02-19 22:59:14 +01:00
|
|
|
pg_stat_statements--1.1--1.2.sql pg_stat_statements--1.0--1.1.sql
|
2014-07-14 20:07:52 +02:00
|
|
|
PGFILEDESC = "pg_stat_statements - execution statistics of SQL statements"
|
2011-02-14 02:06:41 +01:00
|
|
|
|
2015-07-09 02:44:22 +02:00
|
|
|
LDFLAGS_SL += $(filter -lm, $(LIBS))
|
|
|
|
|
2016-11-12 14:01:48 +01:00
|
|
|
REGRESS_OPTS = --temp-config $(top_srcdir)/contrib/pg_stat_statements/pg_stat_statements.conf
|
Expand regression tests of pg_stat_statements for utility queries
This commit adds more coverage for utility statements so as it is
possible to track down all the effects of query normalization done for
all the queries that use either Const or A_Const nodes, which are the
nodes where normalization makes the most sense as they apply to
constants (well, most of the time, really).
This set of queries is extracted from an analysis done while looking at
full dumps of the regression database when applying different levels of
normalization to either Const or A_Const nodes for utilities, as of a
minimal set of these, for:
- All relkinds (CREATE, ALTER, DROP)
- Policies
- Cursors
- Triggers
- Types
- Rules
- Statistics
- CALL
- Transaction statements (isolation level, options)
- EXPLAIN
- COPY
Note that pg_stat_statements is not switched yet to show any
normalization for utilities, still it improves the default coverage of
the query jumbling code (not by as much as enabling query jumbling on
the main regression test suite, though):
- queryjumblefuncs.funcs.c: 36.8% => 48.5%
- queryjumblefuncs.switch.c: 33.2% => 43.1%
Reviewed-by: Bertrand Drouvot
Discussion: https://postgr.es/m/Y+MRdEq9W9XVa2AB@paquier.xyz
2023-02-20 02:16:51 +01:00
|
|
|
REGRESS = pg_stat_statements cursors utility level_tracking planning \
|
|
|
|
cleanup oldextversions
|
2016-11-14 23:53:07 +01:00
|
|
|
# Disabled because these tests require "shared_preload_libraries=pg_stat_statements",
|
|
|
|
# which typical installcheck users do not have (e.g. buildfarm clients).
|
|
|
|
NO_INSTALLCHECK = 1
|
2016-11-12 14:01:48 +01:00
|
|
|
|
2009-01-04 23:19:59 +01:00
|
|
|
ifdef USE_PGXS
|
|
|
|
PG_CONFIG = pg_config
|
|
|
|
PGXS := $(shell $(PG_CONFIG) --pgxs)
|
|
|
|
include $(PGXS)
|
|
|
|
else
|
|
|
|
subdir = contrib/pg_stat_statements
|
|
|
|
top_builddir = ../..
|
|
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
include $(top_srcdir)/contrib/contrib-global.mk
|
|
|
|
endif
|