| 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: | Loles <lolesft(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | |
| Date: | 2021-05-18 13:46:09 |
| Message-ID: | 3079426.1621345569@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Given this, should the configuration description for this include the "This
> parameter can only be set in postgresql.conf file or on the server command
> line." comment,
Hmm, yeah, it does lack the standard boilerplate for a PGC_POSTMASTER
GUC. I wonder which other GUCs are misidentified that way.
> as well as the fact that 0 disables the logical replication
> subscribing feature altogether, and precludes the background worker
> scheduler process from launching at startup?
I'd be in favor of mentioning the former, but the latter seems like
an implementation detail.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-05-18 13:50:46 | Re: |
| Previous Message | David G. Johnston | 2021-05-18 13:41:22 | Re: |