From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(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-12-11 17:34:56 |
Message-ID: | 20151211173456.GS2763@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
Alvaro Herrera wrote:
> Not sure what is going on; my reading of the code certainly says that
> the data should be there. I'm looking into it.
>
> I also noticed that I didn't actually push the whole of the patch
> yesterday -- I neglected to "git add" the latest changes, the ones that
> fix the promotion scenario :-( so the commit messages is misleading
> because it describes something that's not there.
Pushed a fix.
I also wrote some tests using the RecoveryNode stuff submitted by
Michael Paquier. These aren't yet pushed, because we don't have the
framework; once we have that I can push them too. As far as I can tell,
these tests exercise all the cases that have been pointed out so far; I
can see some of them fail if I run on previous commits.
Thanks for the continued testing.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Pietro Pugni | 2015-12-15 02:19:08 | Let's improve the documentation of upper() |
Previous Message | Robert Haas | 2015-12-11 15:11:08 | Re: [HACKERS] max_worker_processes on the standby |
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2015-12-11 17:42:19 | Re: Patch: fix lock contention for HASHHDR.mutex |
Previous Message | Robert Haas | 2015-12-11 17:13:02 | Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY? |