Re: Can we do something to help stop users mistakenly using force_parallel_mode?
От | Andrew Dunstan |
---|---|
Тема | Re: Can we do something to help stop users mistakenly using force_parallel_mode? |
Дата | |
Msg-id | 5431a2ef-ec2f-b0c6-0021-9e8297b31d61@dunslane.net обсуждение исходный текст |
Ответ на | Re: Can we do something to help stop users mistakenly using force_parallel_mode? (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Can we do something to help stop users mistakenly using force_parallel_mode?
|
Список | pgsql-hackers |
On 2023-02-14 Tu 17:32, David Rowley wrote:
On Wed, 15 Feb 2023 at 11:27, Andrew Dunstan <andrew@dunslane.net> wrote:It's just occurred to me that this could break the buildfarm fairly comprehensively. I just took a count and we have 74 members using force_parallel_mode. Maybe we need to keep force_parallel_mode as an alternative spelling for debug_parallel_query until we can get them all switched over. I know it's more trouble ...Yeah, I mentioned in [1] about that and took measures there to keep the old name in place. In the latest patch, there's an entry in map_old_guc_names[] to allow the old name to work. I think the buildfarm will still work ok because of that.
Oops, I missed or forgot that.
What I'm not so sure about is how to go about getting all owners to change the config for versions >= PG16. Is that a question of emailing each owner individually to ask them if they can make the change? Or should we just forever keep the map_old_guc_names[] entry for this?
We'll email them once this is in. Most people are fairly reponsive.
cheers
andrew
-- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: