Skip to content
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

Fix for Error: could not execute revoke query: pq: tuple concurrently updated #352

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

kylejohnson
Copy link
Contributor

@kylejohnson kylejohnson commented Sep 20, 2023

This should be a fix for #178.

From what I can tell, the locks created in pgLockRole and pgLockDatabase were not sufficient to cover cases when we're messing with a schema, such as REVOKE ALL PRIVILEGES ON SCHEMA %s FROM %s.

I created an example in examples/issues/178 in which I was able to reproduce the error in nearly 50% of terraform apply or terraform destroy operations. With this change, the error hasn't been reproduced in over 30 such operations.

@kylejohnson
Copy link
Contributor Author

I'm working on adding test coverage for this issue / fix. The goal is to run the terraform code in examples/issues/178 sequentially some number of times, to consider the test "passed" if all runs complete without any errors, and "failed" if there are any errors.

Go bumped from 1.20 to 1.12.1 in commit 26d632a
@kylejohnson
Copy link
Contributor Author

Tests are failing because examples/issues/178/main.tf specifies

    postgresql = {
      source  = "cyrilgdn/postgresql"
      version = "1.21"
    }

and because TestConcurrentPostgresqlGrant is using terratest, which does things quite differently than the way the rest of the tests are structured.

When developing locally, I build the provider and copy it to the correct location locally on disk, before running examples/issues/178/test.sh, so I need to find a similar way to do this within the go testing environment. Ideas?

* Using terratest just wasn't working out - it isn't designed for testing a provider
* github.com/hashicorp/terraform-plugin-sdk/v2/helper/resource looks like the right option but I don't have the time to learn it right now.
@kylejohnson kylejohnson marked this pull request as ready for review October 31, 2023 19:41
@kylejohnson
Copy link
Contributor Author

@cyrilgdn Could you review this please?

@kylejohnson
Copy link
Contributor Author

I've made a beta release targeting this branch, and in my case, the tuple concurrently updated error has been completely fixed.
version = "1.21.1-beta.1"

@philip-harvey
Copy link

Hi @kylejohnson, thanks for looking at this issue. I'm testing out the beta and am now getting this error:
│ Error: could not get advisory lock for members of role rolenamehere: pq: deadlock detected

This error happens on both postgresql_grant and postgresql_default_privileges

@kylejohnson
Copy link
Contributor Author

Hi @kylejohnson, thanks for looking at this issue. I'm testing out the beta and am now getting this error: │ Error: could not get advisory lock for members of role rolenamehere: pq: deadlock detected

This error happens on both postgresql_grant and postgresql_default_privileges

Could you provide an example of code that recreates your error?

@philip-harvey
Copy link

It's somewhat difficult to recreate since it's timing dependent, but something like this should do it.

resource "postgresql_grant" "grant" {
for_each = local.grants_map
role = each.value.rolename
database = local.database_name
schema = each.value.schema
object_type = each.value.object_type
objects = each.value.objects
privileges = each.value.privileges
}

resource "postgresql_default_privileges" "tables" {
for_each = local.default_table_grants_map
database = local.database_name
role = each.value.rolename
owner = var.db_owner
schema = each.value.schema
object_type = "table"
privileges = each.value.privileges
}

I suspect that the deadlock occurs between the default privileges and the grants since they both apply a ton of table grants

I ended up setting max concurrency back to 1 and this issue went away again.

@pagalba-com
Copy link

I have tested 1.21.1-beta.1 and concurrency issues are not fixed.

The fix provided by giner works. This one not.
Ref: https://github.com/giner/terraform-provider-postgresql/commits/fix_getting_stuck_on_refreshing_postgresql_grant

When terraform is refreshing state, it continuously slows down until gets stuck. Never completes.

May be good to understand would be, that I use provider inside a terraform module I built for quite standard function access.

Then every single function, has own terraform file, which uses module, to create standard function user and access for it.

Even if you run terraform with concurrency 1, and setup database connection limit to 1, still it creates like 20 processes, each for single function, and tries to refresh state for 20 modules.

Please make that giner commit into code, as it looks it works perfectly (build and tested it locally).

Comment on lines +698 to +701
schema := d.Get("schema").(string)
if err := pgLockSchema(txn, schema); err != nil {
return err
}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we do it next to where we call pgLockRole (e.g. around line 171) ?

And actually as schema is optional if postgresql_grant is used at database level, we should put this in the else of if objectType == "database" { line 176

	if objectType == "database" {
		if err := pgLockDatabase(txn, database); err != nil {
			return err
		}
	} else {
		// Obtain a lock to avoid `Error: could not execute revoke query: pq: tuple concurrently updated`
		schema := d.Get("schema").(string)
		if err := pgLockSchema(txn, schema); err != nil {
			return err
		}
	}

@cavila-evoliq
Copy link

@kylejohnson do you have any time to address @cyrilgdn's feedback? The changes you've made here would be helpful for me as we are running into the same issue on #178. This is error is quite inconvenient for me as we need to re-run terraform multiple times so I'd be happy to take a stab at addressing the feedback if needed.

@cyrilgdn cyrilgdn force-pushed the main branch 3 times, most recently from f2c2e47 to dea1401 Compare September 8, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"tuple concurrently updated" error on concurrent GRANT statements
5 participants