1 Release published by 1 person

• 1.11.0

  publishedApr 22, 2025

14 Pull requests merged by 1 person

• conftest is updated

  #260 mergedMay 12, 2025

• [#258] Problems in ProbackupTest and TestBasic(ProbackupTest) are fixed

  #259 mergedMay 12, 2025

• [#235] test_pg_ctl_wait_option detects a port conflict

  #257 mergedMay 7, 2025

• OsOperations::get_tempdir() is added

  #254 mergedMay 6, 2025

• New OsOperations methods: makedir, rmdir

  #253 mergedMay 6, 2025

• LocalOperations::get_single_instance is added

  #252 mergedMay 6, 2025

• [#244] PostgresNode now uses os_ops only

  #245 mergedMay 5, 2025

• [Refactoring] Default port manager functions now use PortManager__Generic and LocalOperations

  #251 mergedMay 5, 2025

• [#249] Fix of port number in NodeBackup::spawn_replica

  #250 mergedMay 4, 2025

• Releasing of reserved port in tests

  #248 mergedMay 4, 2025

• [test] TestTestgresLocal.test_upgrade_node is corrected

  #246 mergedMay 4, 2025

• Testgres tests create log dir in exact place

  #243 mergedMay 1, 2025

• [#240] Using of node.psql with other host and port

  #242 mergedApr 28, 2025

• [FIX] Tests include testgres by right way through import

  #241 mergedApr 25, 2025

1 Pull request opened by 1 person

• [#247] PortManager__Generic uses lock-dirs for reserved ports

  #255 openedMay 6, 2025

5 Issues closed by 1 person

• Problems in ProbackupTest and TestBasic(ProbackupTest)

  #258 closedMay 12, 2025

• Unstable test - TestTestgresCommon::test_pg_ctl_wait_option[remote]

  #235 closedMay 7, 2025

• PostgresNode and ConnectionParams

  #244 closedMay 5, 2025

• [BUG] NodeBackup::spawn_replica does not release a reserved port number during failure

  #249 closedMay 4, 2025

• Run node.psql in a different port

  #240 closedApr 28, 2025

2 Issues opened by 1 person

• Port number 65535 is valid for using

  #256 openedMay 7, 2025

• Using lock files for port reservation

  #247 openedMay 4, 2025