-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
duplicate key value violates unique constraint "pg_type_typname_nsp_index" #55
Comments
Are you able to reproduce the issue using the master branch? There's an fix to the postgres db driver that'll be in the next release: #13 |
We still use the old code. We will try to reproduce with the latest master. |
FYI, the postgres db driver fix I mentioned above is now in the latest release (v3.3.0) |
@dotchev Is this still an issue w/ the latest release? |
@dhui i'm facing the same issue also when using the latest code (with when invoked as follows:
|
Does anyone have steps to reproduce this? Was there an old |
This commit introduces an isolated atomic migrations test command to reliably reproduce these issues: - golang-migrate/migrate#55 - https://github.com/sourcegraph/sourcegraph/issues/1491
Hello! Here's a reproducible test command that runs into this. We're using v4.1.0. |
The problem seems to be that |
This commit makes `ensureVersionTable` atomic. Fixes golang-migrate#55
This commit doesn't seem to fix it unfortunately: tsenart@f6caf3e Nor wrapping it all in a transaction. |
Fix is in master. I'll cut at new release with this fix in ~1 week. |
We hit an error in our tests similar to #235
What bothers me is that this is not
ErrLocked
. So it seems like the lock does not work as expected.Or do I get it wrong?
We use Postgres and we call it like this
We use migrate ver 3.2.0
We use pq driver
The text was updated successfully, but these errors were encountered: