| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "aleksander(at)timescale(dot)com" <aleksander(at)timescale(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Changing "Hot Standby" to "hot standby" |
| Date: | 2022-03-09 07:45:32 |
| Message-ID: | ZR0P278MB09209DB6C4561CC22E35B636D20A9@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>I think one more small change...
> A standby server can also be used for read-only queries, in which case
>- it is called a Hot Standby server. See <xref linkend="hot-standby"/> for
>+ it is called a hot standby server. See <xref linkend="hot-standby"/> for
> more information.
> A standby server can also be used for read-only queries, in which case
>- it is called a Hot Standby server. See <xref linkend="hot-standby"/> for
>+ it is called a <firstterm>hot standby</firstterm> server. See
><xref linkend="hot-standby"/> for
> more information.
Thanks for having a look. Done that way.
Regards
Daniel
| Attachment | Content-Type | Size |
|---|---|---|
| align_hot_standby_v4.patch | text/x-patch | 5.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-03-09 08:06:57 | Re: wal_compression=zstd |
| Previous Message | osumi.takamichi@fujitsu.com | 2022-03-09 07:33:22 | RE: Optionally automatically disable logical replication subscriptions on error |