1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
The relation number is your table ID, i.e the object that the lock is awarded on. The process is is most likely the PID, can you check against stl_connection_log and stl_query (xid) column to identify which one it is?
You can find the ID in https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_TABLE_INFO.html
répondu il y a 10 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 mois
Thanks for your answer!
As you passed me these tips, I´ve runned some querys and here´s what I´ve found out:
I appreciate a lot your support and it´s clearly helping me on the way! Hope I can get new tips by you.
Are you running any cross-database queries? If you have an ra3 instance type this is possible. If you are dc2 it is not.
A single transaction (iirc) can run across multiple databases, and the svv_table_info will only show you the table in that specific database, so you should change your connection if it's a cross-db query. This relation could also possibly be a temporary table that does not exist beyond the session for the query which may be why we see the deadlock.
If you have a support level for your account you can also raise a case, if you share the full error message there (I understand why you may want to edit it in a public forum) they can also help look for the PID/XID I find it unusual that the lock isn't related to one of these as transactions are what are awarded locks as they are opened and closed.