# Issue while syncing data for accounts when enabled aws\_route53resolver\_resolver\_rules table

**URL:** <https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011>\
**Category:** CloudQuery Plugins\
**Tags:** aws\
**Created:** [February 10, 2025, 1:06pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011 "2025-02-10T13:06:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prabhanjali](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/prabhanjali/32/109_2.png) [@Prabhanjali](https://community.cloudquery.io/u/Prabhanjali)\
**Post date:** [February 10, 2025, 1:06pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/1 "2025-02-10T13:06:15Z")

</div>

failed to sync v3 source aws\_xxxxxxxxxxxx: write client returned error (insert): plugin returned error: failed to execute batch with pgerror: severity: ERROR, code: 40P01, message: deadlock detected, detail :Process 27979 waits for ShareLock on transaction 107350228; blocked by process 27985.  
Process 27985 waits for AccessExclusiveLock on tuple (418,3) of relation 281674810 of database 16400; blocked by process 27997.  
Process 27997 waits for ShareLock on transaction 107350194; blocked by process 27979., hint: See server log for query details., position: 0, internal\_position: 0, internal\_query: , where: while inserting index tuple (73,6) in relation “aws\_route53resolver\_resolver\_rules”, schema\_name: , table\_name: , column\_name: , data\_type\_name: , constraint\_name: , file: deadlock.c, line: 1149, routine: DeadLockReport: ERROR: deadlock detected (SQLSTATE 40P01)

---

<div class="post-metadata">

**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\
**Post date:** [February 10, 2025, 1:20pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/2 "2025-02-10T13:20:29Z")

</div>

Hi @Prabhanjali welcome to the community 👋 Can you share your configuration YAML spec and CLI version? The latter you can find by running `cloudquery --version `

---

<div class="post-metadata">

**Author:** ![Prabhanjali](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/prabhanjali/32/109_2.png) [@Prabhanjali](https://community.cloudquery.io/u/Prabhanjali)\
**Post date:** [February 10, 2025, 1:33pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/3 "2025-02-10T13:33:16Z")

</div>

Hi @erez  
AWS version - 23.1.0  
CLI version - v5.20.5  
Postgres version - v7.1.2

---

<div class="post-metadata">

**Author:** ![Prabhanjali](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/prabhanjali/32/109_2.png) [@Prabhanjali](https://community.cloudquery.io/u/Prabhanjali)\
**Post date:** [February 10, 2025, 1:35pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/4 "2025-02-10T13:35:06Z")

</div>

Hi @erez  
I’m getting this issue with this table only, all other tables are working fine. should I need to do something? It’s important for us to stay in these versions itself. Can you give me any fix without altering the versions?

---

<div class="post-metadata">

**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\
**Post date:** [February 10, 2025, 1:52pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/5 "2025-02-10T13:52:14Z")

</div>

> [@Prabhanjali](#):
>
> aws\_route53resolver\_resolver\_rules

Ho @Prabhanjali which Postgres Database version are you using? I recommend updating to the latest one as it might contain bug fixes related to this issue.

Also, the versions you’re using are quite outdated, I recommend updating at least the CLI and Postgres plugin to latest versions

---

<div class="post-metadata">

**Author:** ![Prabhanjali](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/prabhanjali/32/109_2.png) [@Prabhanjali](https://community.cloudquery.io/u/Prabhanjali)\
**Post date:** [February 10, 2025, 2:15pm UTC](https://community.cloudquery.io/t/issue-while-syncing-data-for-accounts-when-enabled-aws-route53resolver-resolver-rules-table/1011/6 "2025-02-10T14:15:42Z")

</div>

Hey @erez all other tables are compatible and only this is incompatible and we are running into issues. can you let us know what are the best things that we can do other than updating the versions??  
we aren’t happy to update the versions and break anything in production now
