From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15492: pg_cancel_backend(pg_backend_pid()) returns true sporadically |
Date: | 2018-11-12 05:19:25 |
Message-ID: | 20181112051925.GB2631@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Nov 12, 2018 at 07:01:21AM +0300, Alexander Lakhin wrote:
> I tried to use the 'make standycheck' approach for two reasons. First,
> it's documented at https://www.postgresql.org/docs/11/regress-run.html
> Second, it allows to test a replication between different minor versions
> (after some setup).
> Will we still have such a possibility, if the tests will be removed?
When doing an upgrade the standby needs to go first, but I can see your
point here. If those tests get moved to a TAP test, then the same set
of binaries would be used for both the standby and the primary, so that
possibility would go away if you would want to set a primary with a
different minor version than the standby.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2018-11-12 07:15:35 | BUG #15497: An error occurred initializing the application server: Failed to launch application server |
Previous Message | Amit Langote | 2018-11-12 04:17:35 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |