mirror of
https://github.com/postgres/postgres.git
synced 2026-03-12 21:54:00 -04:00
661643deda
This fixes two issues with the handling of VacuumParams in vacuum_rel(). This code path has the idea to change the passed-in pointer of VacuumParams for the "truncate" and "index_cleanup" options for the relation worked on, impacting the two following scenarios where incorrect options may be used because a VacuumParams pointer is shared across multiple relations: - Multiple relations in a single VACUUM command. - TOAST relations vacuumed with their main relation. The problem is avoided by providing to the two callers of vacuum_rel() copies of VacuumParams, before the pointer is updated for the "truncate" and "index_cleanup" options. The refactoring of the VACUUM option and parameters done in |
||
|---|---|---|
| .. | ||
| brin | ||
| commit_ts | ||
| delay_execution | ||
| dummy_index_am | ||
| dummy_seclabel | ||
| gin | ||
| injection_points | ||
| ldap_password_func | ||
| libpq_pipeline | ||
| oauth_validator | ||
| plsample | ||
| spgist_name_ops | ||
| ssl_passphrase_callback | ||
| test_aio | ||
| test_bloomfilter | ||
| test_copy_callbacks | ||
| test_custom_rmgrs | ||
| test_ddl_deparse | ||
| test_dsa | ||
| test_dsm_registry | ||
| test_escape | ||
| test_extensions | ||
| test_ginpostinglist | ||
| test_integerset | ||
| test_json_parser | ||
| test_lfind | ||
| test_misc | ||
| test_oat_hooks | ||
| test_parser | ||
| test_pg_dump | ||
| test_predtest | ||
| test_radixtree | ||
| test_rbtree | ||
| test_regex | ||
| test_resowner | ||
| test_rls_hooks | ||
| test_shm_mq | ||
| test_slru | ||
| test_tidstore | ||
| typcache | ||
| unsafe_tests | ||
| worker_spi | ||
| xid_wraparound | ||
| Makefile | ||
| meson.build | ||
| README | ||
Test extensions and libraries ============================= src/test/modules contains PostgreSQL extensions that are primarily or entirely intended for testing PostgreSQL and/or to serve as example code. The extensions here aren't intended to be installed in a production server and aren't suitable for "real work". Furthermore, while you can do "make install" and "make installcheck" in this directory or its children, it is NOT ADVISABLE to do so with a server containing valuable data. Some of these tests may have undesirable side-effects on roles or other global objects within the tested server. "make installcheck-world" at the top level does not recurse into this directory. Most extensions have their own pg_regress tests or isolationtester specs. Some are also used by tests elsewhere in the tree. If you're adding new hooks or other functionality exposed as C-level API this is where to add the tests for it.