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
I am using pg_timetable to reindex concurrently some of my indexes.
While doing the reindex, another query comes and locks the table. At this time an error appears and the command does not get finished.
There is not any error other than the logs I posted. If there is, please guide me to get it then I will post it.
As I explained the reason is the other queries that lock the table,which I am reindexing by the job.I wish the job could wait until they finish and unlock the table.
May be if the time out get increased, the problem would be solved.
Here the time out field is set to 0,but job gets failed as soon as the lock occures.
This is the value of those parameters: idle_in_transaction_session_timeout is set to 600000 statement_timeout is set to 0 idle_session_timeout is not set at all and is not in the .config file.
Activity
pashagolub commentedon Aug 16, 2024
Would you please provide the full error message for
unexpected EOF.Seems like you have connection issues and it's nothing we can do on pg_timetable side.
ArashMasroor commentedon Aug 16, 2024
There is not any error other than the logs I posted. If there is, please guide me to get it then I will post it.
As I explained the reason is the other queries that lock the table,which I am reindexing by the job.I wish the job could wait until they finish and unlock the table.
May be if the time out get increased, the problem would be solved.
Here the time out field is set to 0,but job gets failed as soon as the lock occures.
pashagolub commentedon Aug 16, 2024
There are such things as statement_timeout, idle_in_transaction_session_timeout and idle_session_timeout. And these options are controlled by you. Please make sure the session is not dropped by the server due these settings.
pg_timetable has timeouts for chains and tasks. Default value 0 means wait forever.
ArashMasroor commentedon Aug 19, 2024
Sorry for the delay.
This is the value of those parameters:
idle_in_transaction_session_timeout is set to 600000
statement_timeout is set to 0
idle_session_timeout is not set at all and is not in the .config file.