postgresql/src/test/modules/test_pg_dump
Daniel Gustafsson 936e3fa378 Drop global objects after completed test
Project policy is to not leave global objects behind after a regress
test run.  This was found as a result of the development of a patch
to make pg_regress detect such leftovers automatically, which in the
end was withdrawn due to issues with parallel runs.

Discussion: https://postgr.es/m/E1phvk7-000VAH-7k@gemulon.postgresql.org
2024-04-03 13:33:25 +02:00
..
expected Drop global objects after completed test 2024-04-03 13:33:25 +02:00
sql Drop global objects after completed test 2024-04-03 13:33:25 +02:00
t Add "--exclude-extension" to pg_dump's options. 2024-03-20 08:05:44 +00:00
.gitignore Add TAP tests for pg_dump 2016-05-06 14:06:50 -04:00
Makefile Add PGXS options to control TAP and isolation tests, take two 2018-12-03 09:27:35 +09:00
README Fix possible future cache reference leak in ALTER EXTENSION ADD/DROP. 2020-04-17 13:41:59 -04:00
meson.build Update copyright for 2024 2024-01-03 20:49:05 -05:00
test_pg_dump--1.0.sql Don't try to dump RLS policies or security labels for extension objects. 2023-11-13 17:04:26 -05:00
test_pg_dump.control Add TAP tests for pg_dump 2016-05-06 14:06:50 -04:00

README

test_pg_dump is an extension explicitly to test pg_dump when
extensions are present in the system.

We also make use of this module to test ALTER EXTENSION ADD/DROP.