Re: Issue with bgworker, SPI and pgstat_report_stat

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Issue with bgworker, SPI and pgstat_report_stat
Дата
Msg-id 20160707180656.fu6iojkket5o43nb@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Issue with bgworker, SPI and pgstat_report_stat  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Issue with bgworker, SPI and pgstat_report_stat  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On 2016-07-07 14:04:36 -0400, Robert Haas wrote:
> On Thu, Jul 7, 2016 at 1:52 PM, Julien Rouhaud
> <julien.rouhaud@dalibo.com> wrote:
> > Should a bgworker modifing data have to call pgstat_report_stat() to
> > avoid this problem? I don't find any documentation suggesting it, and it
> > seems that worker_spi (used as a template for this bgworker and I
> > suppose a lot of other one) is also affected.
> 
> That certainly seems like the simplest fix.  Not sure if there's a better one.

I think a better fix would be to unify the startup & error handling
code. We have way to many slightly diverging copies. But that's a bigger
task, so I'm not protesting against making a more localized fix.

Andres



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Reviewing freeze map code
Следующее
От: Robert Haas
Дата:
Сообщение: Re: primary_conninfo missing from pg_stat_wal_receiver