Reindex concurrently using pg_timetable #659
Replies: 4 comments
-
Would you please provide the full error message for Seems like you have connection issues and it's nothing we can do on pg_timetable side. |
Beta Was this translation helpful? Give feedback.
-
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. Here the time out field is set to 0,but job gets failed as soon as the lock occures. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Sorry for the delay. This is the value of those parameters: |
Beta Was this translation helpful? Give feedback.
-
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.
Here is my config:
Here is the execution log:
Here is the timetable log:
How is it possible to overcome this error?
Beta Was this translation helpful? Give feedback.
All reactions