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
Is your feature request related to a problem? Please describe.
For the initialization process pg_chameleon will issue FLUSH TABLES WITH READ LOCK on a source database (MySQL) to get transactional snapshot. This action can be blocked with long running transaction on a table and pg_chameleon could wait very log time if lock_wait_timeout is not configured.
It would be nice to be able to specify lock timeout as FTWRL could be risky operation in some production workloads.
Describe the solution you'd like
Implement lock_wait_timeout option for source (MySQL) database. It would be nice to be able set lock_wait_timeout just for pg_chameleon session not affecting others.
Also, I think current config is not intuitive as I would assume that lock_timeout specified under the source database (MySQL) is related to the locks on the MySQL not target database (Postgres).
Thank you
The text was updated successfully, but these errors were encountered:
markosutic
changed the title
Implement lock_wait_timeout option for source database (MySQL)
Implement lock_wait_timeout option for the source database (MySQL)
Nov 23, 2022
Is your feature request related to a problem? Please describe.
For the initialization process
pg_chameleon
will issueFLUSH TABLES WITH READ LOCK
on a source database (MySQL) to get transactional snapshot. This action can be blocked with long running transaction on a table andpg_chameleon
could wait very log time iflock_wait_timeout
is not configured.It would be nice to be able to specify lock timeout as FTWRL could be risky operation in some production workloads.
Describe the solution you'd like
Implement
lock_wait_timeout
option for source (MySQL) database. It would be nice to be able setlock_wait_timeout
just forpg_chameleon
session not affecting others.Also, I think current config is not intuitive as I would assume that
lock_timeout
specified under the source database (MySQL) is related to the locks on the MySQL not target database (Postgres).Thank you
The text was updated successfully, but these errors were encountered: