You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,8 +34,9 @@ The first is that the creation of the second and any subsequent empty database i
34
34
as the library can reuse the existing container instead of wasting time by starting another one.
35
35
36
36
The second is that storing all databases in a single container makes it possible to efficiently transfer or share data across databases.
37
-
This is a prerequisite for the [refresh mode](#refreshing-the-database-during-tests),
38
-
which can make a fast binary copy of the database (using a [template database](https://www.postgresql.org/docs/current/manage-ag-templatedbs.html) if possible) before the test is started to isolate it from other tests.
37
+
This is the main prerequisite for the [refresh mode](#refreshing-the-database-during-tests),
38
+
which can make a fast binary copy of the database (using a [template database](https://www.postgresql.org/docs/current/manage-ag-templatedbs.html) if possible)
39
+
before the test is started to make the test completely isolated from other tests, even if changes have been committed to the database.
39
40
This approach effectively rolls back any changes made by the test and ensures that even refreshing larger databases takes only a few milliseconds.
40
41
41
42
In addition, there are some other optimization techniques to increase overall performance,
0 commit comments