Re: POC: Cleaning up orphaned files using undo logs
От | Robert Haas |
---|---|
Тема | Re: POC: Cleaning up orphaned files using undo logs |
Дата | |
Msg-id | CA+Tgmoavy8hyi0K=cnrvQF9rb09ya4XvxYss5uS4hx_xVPpcZg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: POC: Cleaning up orphaned files using undo logs (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: POC: Cleaning up orphaned files using undo logs
|
Список | pgsql-hackers |
On Tue, Jun 25, 2019 at 4:00 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > Fair enough. I have implemented it based on next_retry_at and use > constant time 10s for the next retry. I have used define instead of a > GUC as all the other constants for similar things are defined as of > now. One thing to note is that we want the linger time (defined as > UNDO_WORKER_LINGER_MS) for a undo worker to be more than failure retry > time (defined as UNDO_FAILURE_RETRY_DELAY_MS) as, otherwise, the undo > worker can exit before retrying the failed requests. Uh, I think we want exactly the opposite. We want the workers to exit before retrying, so that there's a chance for other databases to get processed, I think. Am I confused? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: