Re: [PATCH] SET search_path += octopus
От | Abhijit Menon-Sen |
---|---|
Тема | Re: [PATCH] SET search_path += octopus |
Дата | |
Msg-id | 20201021043540.GA724274@toroid.org обсуждение исходный текст |
Ответ на | Re: [PATCH] SET search_path += octopus (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: [PATCH] SET search_path += octopus
|
Список | pgsql-hackers |
At 2020-10-20 10:53:04 -0700, andres@anarazel.de wrote: > > > postgres=# ALTER SYSTEM SET max_worker_processes += 4; > > ALTER SYSTEM > > Much less clear that this is a good idea... I agree it's less clear. I still think it might be useful in some cases (such as the example with max_worker_processes quoted above), but it's not as compelling as altering search_path/shared_preload_libraries. (That's partly why I posted it as a separate patch.) > It seems to me that appending and incrementing using the same syntax > is a) confusing b) will be a limitation before long. I understand (a), but what sort of limitation do you foresee in (b)? Do you think both features should be implemented, but with a different syntax, or are you saying incrementing should not be implemented now? > > These patches do not affect configuration file parsing in any way: > > its use is limited to "SET" and "ALTER xxx SET". > > Are you including user / database settings as part of ALTER ... SET? > Or just SYSTEM? Yes, it works the same for all of the ALTER … SET variants, including users and databases. -- Abhijit
В списке pgsql-hackers по дате отправления: