Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: postgrespro/testgres

1.11.1

28 Aug 07:42
Compare
Choose a tag to compare
Loading

What's Changed

Full Changelog:1.11.0...1.11.1

Changes in testgres code

  • [#240] Using ofnode.psql with other host and port in#242
  • [#249] Fix of port number leak inNodeBackup::spawn_replica in#250
  • [Refactoring] Default port manager functions now usePortManager__Generic andLocalOperations in#251
  • [#244]PostgresNode now usesos_ops only in#245
  • LocalOperations::get_single_instance is added in#252
  • NewOsOperations methods:makedir,rmdir in#253
  • OsOperations::get_tempdir() is added in#254
  • [#256] Port number 65535 is valid for using in#268
  • [#264] New propertyPostgresNode::port_manager in#269
  • PortManager__Generic sends debug messages "port is reserved/released" in#270
  • [#266]OsOperations::build_path is added in#273
  • A support ofcwd parameter is added toOsOperations::exec_command in#272
  • [#274] Unusedshould_rm_dirs is deleted (cleanup) in#275
  • [python v3.13]TestTestgresCommon::test_logging useslogging._lock in#276
  • NodeApp is refactored in#278
  • Testgres is tested on python 3.7 now, too in#280
  • Remove usage of not standard function nc inremote_ops.py is_port_free in#284

Changes in testgres tests

  • [FIX] Tests include testgres by right way through import in#241
  • Testgres tests create log dir in exact place in#243
  • [test]TestTestgresLocal.test_upgrade_node is corrected in#246
  • Releasing of reserved port in tests in#248
  • [#235]test_pg_ctl_wait_option detects a port conflict in#257
  • Incomplete asserts in are fixed (conftest) in#261
  • [tests] Creation of "dummy/empty" log file for xdist controller is fixed in#282
  • conftest is updated - ExitStatusNames in#283

Our plans

Split testgres' code

We will move the content of testgres/operations folder into the separated package - testgres.os_ops.

Some exceptions will be moved in separated packages testgres.common, too.

It allows to use these things separately.

This change requires to the internal reorganization of testgres source code - 'testgres' folder will be renamed with 'src'.

Remove testgres.plugins

We will remove testgres.plugins folder with all its content (plugin for pg_probackup2).

Plugin for pg_probackup2 was already moved to the separated package -https://github.com/postgrespro/testgres-pg_probackup2

If you download testgres-pg-probackup2 from github directly, please update your code to avoid any problem in the near future.

Contributors

Contributors

  • @dmitry-lipetsk
  • @demonolock
dmitry-lipetsk and demonolock
Assets2
Loading

1.11.0

22 Apr 12:07
Compare
Choose a tag to compare
Loading

Testgres 1.11.0 Release Notes

1. Important Changes

1.1. Removal oftestgres.OsOperations::db_connect method (#237)

Thedb_connect method has been removed from theOsOperations interface as it was not fitting with the OS-specific functionality it was intended for.

1.2. Replacement oftestgres.helpers.port_manager.PortManager (#234)

The oldPortManager class has been replaced by the newtestgres.port_manager.PortManager interface. The functionalities of the oldPortManager are now in thetestgres.utils.internal__reserve_port function.

1.3.PostgresNode property changes (#234)

  • PostgresNode::name,PostgresNode::host,PostgresNode::port,PostgresNode::ssh_key, andPostgresNode::os_ops are now read-only properties. These properties cannot be modified after the creation of aPostgresNode object.
  • Modifying a node's port now requires recreating thePostgresNode object due to potential complexities in synchronizing configurations across PostgreSQL instances.

1.4. NewPostgresNode parameters (#234,ac0a2bb)

  • port_manager andos_ops parameters have been added to thePostgresNode constructor. These parameters allow explicit control over the port reservation and the OS operations used by the node.

2. New Features

2.1. Newtestgres.port_manager.PortManager Interface (#234)

A new interface for reserving and releasing ports, used byPostgresNode to manage port assignments correctly on both local and remote systems. Two implementations are available:

  • PortManager__ThisHost (for local systems)
  • PortManager__Generic (for both local and remote systems)

2.2.PostgresNode::clone_with_new_name_and_base_dir Method (ac0a2bb)

New method to clone aPostgresNode with a new name and base directory. This method is now used inNodeBackup::spawn_primary for better node cloning.

2.3.OsOperations::is_free_port Method (#234)

A new method added toOsOperations to check if a port is free. This method is used in the newPortManager__Generic class.

2.4. Support for Environment Variables inOsOperations::execute_command (#239)

You can now pass environment variables through the newexec_env parameter when using theexecute_command method ofOsOperations. This feature has been added toPostgresNode::start andPostgresNode::slow_start.

3. Updates and Changes

3.1.PostgresNode::start Does Not Calllogging.error Anymore (b917141)

ThePostgresNode::start method no longer logs errors before raising exceptions. This change improves the handling of errors and avoids misclassification of errors as they are now left for the client to handle.

3.2.RemoteOperations::exec_command Updates (#185,#187)

  • Explicit enumeration of supportedcmd parameter types.
  • Explicitly transfers language environment variables (LANG,LC_*, etc.) during SSH command execution.

3.3.PostgresNode::pid Improved (#199)

Now usespg_ctl to handlepid property more reliably.

3.4. Refactoring ofOsOperations::execute_command (#203)

Improved error handling and the way results are processed. The function now only checks the exit code for errors and allows the caller to manage expected errors.

4. Bug Fixes

4.1.OsOperations::cwd Bug Fix (#182)

The implementation ofcwd now works correctly with local systems.

4.2. Fixes inOsOperations::write Method (#183)

Bug fixes and data preparation improvements for both local and remote operations.

4.3. Fixes inPostgresNode::start Method (50fc4c5)

Corrected an issue in the warning message generation when starting a node.

4.4.RemoteOperations::mktemp Fix (#202)

The call tomktemp now correctly uses the-t option to return the full path instead of just a name.

4.5. Fix forRemoteOperations::listdir (#217)

Improved handling of directory listings, especially for paths with spaces.

5. Other Changes

5.1. New CI Verifications

  • Support for multiple Python versions (3.8 - 3.12).
  • Tests on multiple Linux distributions (Ubuntu 2024.04, AltLinux 10/11).

5.2. Migration topytest

Tests have been migrated fromunittest topytest for better flexibility and efficiency.

5.3. Global Test Refactoring

New unified tests forLocalOperations andRemoteOperations.

5.4. Experimental Logging Feature

A newconftest.py allows logging test results for further processing of errors and warnings within a single test.

Full Changelog:1.10.5 → 1.11.0

Contributors

Contributors

  • @dmitry-lipetsk
dmitry-lipetsk
Loading

1.10.5

18 Feb 13:46
Compare
Choose a tag to compare
Loading

What's Changed

Full Changelog:1.10.4...1.10.5

Contributors

  • @dmitry-lipetsk
dmitry-lipetsk
Loading
dmitry-lipetsk reacted with laugh emoji
1 person reacted

1.10.4

12 Feb 08:38
Compare
Choose a tag to compare
Loading

Testgres 1.10.4 Release Notes

🚀 Key Improvements

  • Better Port Management: Improved handling of port numbers to reduce conflicts and errors.#165@dmitry-lipetsk
  • More Reliable Error Handling:

🔧 Bug Fixes & Enhancements

  • Database Connection Fix:PSQL now explicitly passes the database name using-d <dbname>.#168@dmitry-lipetsk
  • SSH Command Fix: Corrected SSH command execution inRemoteOperations::execute.#169@dmitry-lipetsk
  • Remote Operations Updates:
  • File Operations Enhancements:
  • Backup Testing Support: Addedcheck backup-source to help testpg_probackup3.#176@egarbuz

🛠 Refactoring & Code Cleanup

🎉 New Contributors

📌Full Changelog:1.10.3 → 1.10.4

Contributors

  • @dmitry-lipetsk
  • @egarbuz
dmitry-lipetsk and egarbuz
Loading
dmitry-lipetsk reacted with hooray emoji
1 person reacted

1.10.3

15 Dec 17:31
Compare
Choose a tag to compare
Loading

What's Changed

New Contributors

Full Changelog:1.10.2...1.10.3

Contributors

  • @kianmeng
  • @demonolock
  • @dura0ok
  • @MakSl
  • @MetalDream666
kianmeng, demonolock, and 3 other contributors
Loading

1.10.2

27 Sep 15:09
177724b
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

What's Changed

New Contributors

Full Changelog:1.10.1...1.10.2

Contributors

  • @demonolock
  • @dura0ok
  • @asavchkov
  • @egarbuz
demonolock, dura0ok, and 2 other contributors
Loading

1.10.1

08 Jul 04:18
Compare
Choose a tag to compare
Loading

What's Changed

New Contributors

Full Changelog:1.10.0...1.10.1

Contributors

  • @fabriziomello
  • @demonolock
  • @MakSl
  • @MetalDream666
  • @egarbuz
fabriziomello, demonolock, and 3 other contributors
Loading

1.10.0

14 Mar 14:13
356cd52
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

What's Changed

  • Add pg_upgrade option by@demonolock (#97)
    This function allows upgrade PostgreSQL versions.
  • Remove unnecessary output by@homper (#88)
  • Fix get_pg_version for Linux Mint by@demonolock (#101)
  • Set default test locale to en by@Ogurezzz (#107)
    This change aims to standardize test outputs.
  • Fix Error during executing query by@z-kasymalieva (#110)
    Resolved an issue related to executing queries within the framework, particularly when executing commands that do not produce row output, which previously resulted in errors.
  • Run the archive command through exec by@asavchkov (#113)
    If the PostgreSQL archive command is run through the dash shell the shell produces a core dump upon receiving a SIGQUIT during the PostgreSQL server shutdown. This change replaces the dash process with pg_probackup to avoid the production of a core dump.

New Contributors

Full Changelog:1.9.3...1.10.0

Contributors

  • @demonolock
  • @homper
  • @Ogurezzz
  • @asavchkov
  • @z-kasymalieva
demonolock, homper, and 3 other contributors
Loading

1.9.3

21 Dec 11:48
1a2f6da
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading
  • Fixed a problem on MacOS with command --version
  • Fixed problems on Windows
Loading

1.9.2

19 Oct 21:33
Compare
Choose a tag to compare
Loading
  • Removed sshtunnel and fabric libraries usage
Loading
Previous13
Previous

[8]ページ先頭

©2009-2025 Movatter.jp