On Wed, Sep 10, 2025 at 01:02:46PM -0700, David G. Johnston wrote: > * NB: see GucSource_Names in guc.c if you change this. > > The constant was moved to guc_tables.c I would just remove the file reference. Knowing that GucSource_Names matters is enough to grep for it. Documenting its location does not matter. > Also, these seem like they should be documented for pg_settings.source > > Per recent complaint: > https://www.postgresql.org/message-id/04f101dc2288$121b2de0$365189a0$@msym.fr Yeah, why not. Listing all of them GucSource_Names directly in the docs may help if that clarifies things regarding some of the values. The last additions in the list were 9475db3a4eb5 and f480e2944985, if my grepping gets it right, pointing that this has a low risk of rotting when a new one is added to the code, and forgotten in the docs. -- Michael
On Thu, Sep 11, 2025 at 08:48:47AM +0900, Michael Paquier wrote: > I would just remove the file reference. Knowing that GucSource_Names > matters is enough to grep for it. Documenting its location does not > matter. Actually, it matters, as GucSource_Names and GucSource need to be kept in sync. I've fixed the comment for now down to v16. -- Michael
On Thu, Sep 11, 2025 at 08:48:47AM +0900, Michael Paquier wrote:
> I would just remove the file reference. Knowing that GucSource_Names
> matters is enough to grep for it. Documenting its location does not
> matter.
Actually, it matters, as GucSource_Names and GucSource need to be kept
in sync. I've fixed the comment for now down to v16.
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера