| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, David Steele <david(at)pgmasters(dot)net>, David Zhang <david(dot)zhang(at)highgo(dot)ca>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Nicer error when connecting to standby with hot_standby=off |
| Date: | 2021-03-09 14:17:22 |
| Message-ID: | 20210309141722.GA8618@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Mar-09, James Coleman wrote:
> Yes, I think they both agreed on the "DETAIL: Hot standby mode is
> disabled." message, but that alternative meant not needing to add any
> new signals and pm states, correct?
Ah, I see! I was thinking that you still needed the state and signal in
order to print the correct message in hot-standby mode, but that's
(obviously!) wrong. So you're right that no signal/state are needed.
Thanks
--
Álvaro Herrera Valdivia, Chile
Si no sabes adonde vas, es muy probable que acabes en otra parte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2021-03-09 14:19:37 | Re: Nicer error when connecting to standby with hot_standby=off |
| Previous Message | David Steele | 2021-03-09 14:12:31 | Re: Enhance traceability of wal_level changes for backup management |