Fabrízio de Royes Mello 0ae6f95646 Use DROP DATABASE ... WITH (FORCE) on tests
PG13 introduced an option to DROP DATABASE statement to terminate all
existing connections to the target database. Now that our minor
supported version is PG13 make sense to use it on regression tests in
order to avoid potential flaky tests.
2023-09-26 14:35:23 -03:00
..
2022-03-01 13:15:46 +01:00
2021-04-23 09:57:41 +02:00
2022-03-01 13:15:46 +01:00
2020-10-13 18:06:28 +02:00
2023-07-12 23:56:04 +02:00
2020-10-13 18:06:28 +02:00
2020-10-13 18:06:28 +02:00
2020-10-13 18:06:28 +02:00
2022-03-01 13:15:46 +01:00
2022-03-01 13:15:46 +01:00
2022-03-15 15:04:30 -03:00
2021-01-28 15:04:30 +01:00
2021-09-22 18:20:30 +02:00
2020-06-02 23:48:35 +02:00
2021-03-04 11:48:49 +01:00

Testing using multiple versions

This tests creates multiple instances with different upgrade scenarios:

CONTAINER_UPDATED:

  • install previous version
  • run test setup script
  • update container
  • ALTER EXTENSION UPDATE

CONTAINER_CLEAN_RERUN:

  • install main
  • run test setup script

CONTAINER_CLEAN_RESTORE:

  • dump CONTAINER_UPDATED with pg_dump
  • restore in new container

After those steps the test post script is run on all instances and the output diffed, throwing an error if there is a difference between any of the instances.