| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: pg_rewind exiting with error code 1 when source and target are on the same timeline |
| Date: | 2015-12-15 19:50:25 |
| Message-ID: | 56706F01.9040202@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 12/12/15 6:08 AM, Michael Paquier wrote:
>> I committed this to master. It's also on the 9.5 open item list, but if
>> I backport it then the tests don't pass. Still looking. Not sure yet
>> if this is because of code changes in pg_rewind master or test
>> infrastructure changes in master.
>
> The failure is as follows:
> source data directory must be shut down cleanly
> Failure, exiting
> not ok 1 - pg_rewind local
>
> And is caused by the fact that master checks that the source node has
> been stopped with DB_SHUTDOWNED and not DB_SHUTDOWNED_IN_RECOVERY.
It seems that the/a problem is actually that the test setup tries a
rewind using the standby as the source and the standby also as the
target. The source should be the primary, and then it doesn't matter
whether we allow DB_SHUTDOWNED_IN_RECOVERY. Need to check that test setup.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-15 20:15:59 | Re: pg_rewind exiting with error code 1 when source and target are on the same timeline |
| Previous Message | David G. Johnston | 2015-12-15 19:50:02 | Re: BUG #13819: What is maximum limit on max_connections? |