| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rajni Baliyan <saan654(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Ankush Chawla <ankushchawla03(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: hot standby in Postgresql 12 |
| Date: | 2021-01-19 22:03:47 |
| Message-ID: | CAKFQuwYqSG6dLm-rFQWxhzPqPmviK_Ft9VR2Qn=2U0nRhubnHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Jan 19, 2021 at 2:56 PM Rajni Baliyan <saan654(at)gmail(dot)com> wrote:
> As David highlighted,
> >> I took the error from the cp command to mean that this was in fact a
> warm standby regardless of any claims by the poster. I’ll readily admit I
> am not that familiar with this stuff though.
> Seems your archive command is not working properly. Set it first and then
> try again.
>
Don't think so - as Laurenz noted the last line reads:
"2021-01-18 07:31:01.043 UTC [21079]LOG: started streaming WAL from
primary at 0/35000000 on timeline 3"
Which indicates that streaming is supposedly working even though the
expected data hasn't made it from the primary to the standby.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajni Baliyan | 2021-01-19 23:15:59 | Re: hot standby in Postgresql 12 |
| Previous Message | Rajni Baliyan | 2021-01-19 21:55:54 | Re: hot standby in Postgresql 12 |