Use Postgres.conn rather than Postgres.db to handle table locking #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#2 makes it so that
WithInstance
in thepgx
database driver simply grabs a connection from the pool and callsWithConnection
on it.However, golang-migrate#992 has added the ability to configure the
pgx
driver to use either advisory or table locks to lock the database for migrations.This PR updates the functions that acquire and release those table locks to use
Postgres.conn
rather thanPostgres.db
, as following the changes in #2 allPostgres
instances will haveconn
set but those instantiated withWithConnection
may not havedb
set.