| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | konkove(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Corresponding documentation page does not mention about `spread` mode |
| Date: | 2023-10-03 22:44:37 |
| Message-ID: | 2465735.1696373077@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Oct 3, 2023 at 2:48 PM PG Doc comments form <noreply(at)postgresql(dot)org>
> wrote:
>> But mentioned section 26.3.3 does not describe `spread` mode:
> It does, though it is phrased in terms of "fast => false" meaning "spread"
> whereas "fast => true" means "immediate".
> But since the CLI wanted a label instead of true/false it had to call the
> default "not fast" mode something and it chose "spread".
> Not saying this couldn't be made more clear/better but it is accurate and
> complete.
Perhaps a parenthetical remark like "(pg_basebackup refers to this as
'spread' mode)" would help?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Fredouille | 2023-10-04 00:40:40 | Re: unnest multirange, returned order |
| Previous Message | Brad White | 2023-10-03 22:34:01 | ODBC options |