| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Pg_upgrade and collation |
| Date: | 2016-06-28 21:21:51 |
| Message-ID: | 20160628212151.GC11193@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Jun 20, 2016 at 11:16:36AM -0400, Bruce Momjian wrote:
> In looking at the docs, it seems it would go in the Backup section
> somewhere:
>
> https://www.postgresql.org/docs/9.6/static/backup.html
>
> Seems it would apply to both of these backup sections:
>
> 24.2. File System Level Backup
> 24.3. Continuous Archiving and Point-in-Time Recovery (PITR)
>
> and also here:
>
> 25.2. Log-Shipping Standby Servers
>
> It seems odd to put it in all of these places, but where can we
> centrally put it?
In looking at the docs, I found that the section "Creating a Database
Cluster", which covers initdb and collations, as the best place to put
this warning. Patch attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| Attachment | Content-Type | Size |
|---|---|---|
| collation.diff | text/x-diff | 875 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-06-28 21:58:58 | Re: Pg_upgrade and collation |
| Previous Message | Bruce Momjian | 2016-06-28 20:09:23 | Re: effective_io_concurrency and SSDs |