Re: Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)
Дата
Msg-id 28424.1349366400@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Ответы Re: Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)
Список pgsql-hackers
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> So I propose the attached patch. I made small changes to postgres.c to 
> make it call exec_replication_command() instead of exec_simple_query(), 
> and reject extend query protocol, in a WAL sender process. A lot of code 
> related to handling the main command loop and signals is removed from 
> walsender.c.

Why do we need the forbidden_in_wal_sender stuff?  If we're going in
this direction, I suggest there is little reason to restrict what the
replication client can do.  This seems to be both ugly and a drag on
the performance of normal backends.
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: bison location reporting for potentially-empty list productions
Следующее
От: Boszormenyi Zoltan
Дата:
Сообщение: Re: [PATCH] Make pg_basebackup configure and start standby [Review]