Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on?
| От | Peter Eisentraut |
|---|---|
| Тема | Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on? |
| Дата | |
| Msg-id | 00942f25-e31f-b38d-4654-52beaf942603@2ndquadrant.com обсуждение |
| Ответ на | Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on? (Petr Jelinek <petr.jelinek@2ndquadrant.com>) |
| Ответы |
Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on?
|
| Список | pgsql-hackers |
On 4/18/17 22:13, Petr Jelinek wrote: > So my idea was to add some kind of inuse flag. This turned out to be bit > more complicated in terms of how to clean it than I would have hoped. > This is due to the fact that there is no way to reliably tell if worker > has failed to start if the parent worker crashed while waiting. > > My solution to that is to use similar logic to autovacuum where we use > timeout for worker to attach to shmem. We do this only if there is no > free slot found when launch of replication worker was requested. It looks like launch_time is never set the current time in your patch. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: