Re: Changing the setting of wal_sender_timeout per standby
От | Michael Paquier |
---|---|
Тема | Re: Changing the setting of wal_sender_timeout per standby |
Дата | |
Msg-id | 20180919054031.GA19808@paquier.xyz обсуждение исходный текст |
Ответ на | RE: Changing the setting of wal_sender_timeout per standby ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
Ответы |
Re: Changing the setting of wal_sender_timeout per standby
RE: Changing the setting of wal_sender_timeout per standby |
Список | pgsql-hackers |
On Wed, Sep 19, 2018 at 12:14:57AM +0000, Tsunakawa, Takayuki wrote: > From: Masahiko Sawada [mailto:sawada.mshk@gmail.com] > > I didn't follow the first sentence of the above hunk. Is the > > wal_sender_timeout relevant with %q? > > Ouch, that's a careless mistake. I copied the paragraph from another > parameter and failed to remove some sentence. Patch revised. - A value of zero disables the timeout mechanism. This parameter - can only be set in - the <filename>postgresql.conf</filename> file or on the server - command line. + A value of zero disables the timeout mechanism. + Only superusers can change this parameter at session start, + and it cannot be changed at all within a session. The default value is 60 seconds. Parameters classified as PGC_BACKEND can be updated by any users, and those marked as PGC_SU_BACKEND can only be updated by superusers. Replication users are not superusers, which is why PGC_BACKEND is most adapted. Your description should just say "This parameter cannot be changed after session start. -- Michael
Вложения
В списке pgsql-hackers по дате отправления: