Re: [HACKERS] max_worker_processes on the standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, oonishitk(at)nttdata(dot)co(dot)jp, pgsql-docs <pgsql-docs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] max_worker_processes on the standby
Date: 2015-10-30 10:30:17
Message-ID: CA+TgmoasssOk0n1whCqZAzewkt88_y_mk5E5JMR-qGa_b6dXSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Thu, Oct 29, 2015 at 5:41 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> I found another strange behavior on track_commit_timestamp.
> Here are the steps to reproduce it.
>
> 1. Start the master and standby servers with track_commit_timestamp enabled.
> Since committs is activated in standby, pg_last_committed_xact() can
> successfully return the timestamp of last transaction as expected.
>
> 2. Disable track_commit_timestamp in the master and restart the master server.
> The parameter-change WAL record is streamed to the standby and committs
> is deactivated. pg_last_committed_xact() causes an ERROR in the standby.
>
> 3. Run checkpoint in the master.
>
> 4. Run restartpoint in the standby after the checkpoint WAL record generated
> in #3 is replicated to the standby.
>
> 5. Restart the standby server.
> Committs is activated in the standby because track_commit_timestamp is
> enabled.

This seems wrong already at this point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Alexander Lakhin 2015-10-30 13:40:53 Re: Moving documentation to XML
Previous Message Fujii Masao 2015-10-29 16:41:13 Re: [DOCS] max_worker_processes on the standby

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-10-30 11:01:13 Re: plpgsql - DECLARE - cannot to use %TYPE or %ROWTYPE for composite types
Previous Message Robert Haas 2015-10-30 10:24:25 ParallelContexts can get confused about which worker is which