Should we warn users about SETs which have no effect?

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Should we warn users about SETs which have no effect?
Дата
Msg-id 4AE72178.1020506@agliodbs.com
обсуждение исходный текст
Ответы Re: Should we warn users about SETs which have no effect?  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
Дерево обсуждения 
Hackers,

There are some GUCs you can set in a context which will accept them, yet
they have no effect when you do.  For example, I can call SET
statement_timeout inside a function, and it has no effect whatsoever.

I'm wondering if we should be throwing a warning in these cases.  And
how many such cases there are.  Thoughts?

--Josh Berkus

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jeff Davis
Дата:
Сообщение: Re: Scaling up deferred unique checks and the after trigger queue
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Proposal: String key space for advisory locks