Re: Parallelizing startup with many databases
| От | Jelte Fennema-Nio |
|---|---|
| Тема | Re: Parallelizing startup with many databases |
| Дата | |
| Msg-id | DFFCCXWS454O.20DU4HLZ89CUQ@jeltef.nl обсуждение исходный текст |
| Ответы |
Re: Parallelizing startup with many databases
|
| Список | pgsql-docs |
On Sat, 3 Jan 2026 at 20:09, Andreas Karlsson <andreas@proxel.se> wrote: > > On 1/3/26 1:58 AM, Jelte Fennema-Nio wrote: > > PS It took me way to long to find that setting. I think we should move > > it from the error handling docs page to the page with all of the other > > recovery settings. https://www.postgresql.org/docs/current/runtime- > > config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY <https://www.postgresql.org/ > > docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY> > > I agree that it is currently not in exactly a great location but the > issue is that the "Recovery" section is a subsection of the "WAL" > section, and syncing the data directory is only loosely related to WAL. > One could argue it is related to WAL as in that it is something done > before replaying WAL but it is not an obvious location either. Or is it? <Moving this discussion to pgsql-docs, with accompanying patch> While the setting is not strictly related to WAL it still seems a much more natural place than the "Error handling" page. Especially because of the description of this subheading: > This section describes the settings that apply to recovery in general, > affecting crash recovery, streaming replication and archive-based > replication. The only recovery related GUC that exists that's not on the WAL page is recovery_min_apply_delay, which is under the Replication->Standby section. Since that GUC is only valid on standbys that seems like a sensible choice.
Вложения
В списке pgsql-docs по дате отправления: