Re: Make query ID more portable

Поиск
Список
Период
Сортировка
От Andrey Lepikhov
Тема Re: Make query ID more portable
Дата
Msg-id b2de55f4-d1d5-cfed-29ce-2dd7d5d281f9@postgrespro.ru
обсуждение исходный текст
Ответ на Re: Make query ID more portable  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: Make query ID more portable
Список pgsql-hackers
On 12/10/21 18:45, Bruce Momjian wrote:
> On Tue, Oct 12, 2021 at 09:40:47AM -0400, Tom Lane wrote:
>> Andrey Lepikhov <a.lepikhov@postgrespro.ru> writes:
>>> But core jumbling code is good, fast and much easier in support.
> Also, the current code handles renames of schemas and objects, but this
> would not.
Yes, It is good option if an extension works only in the context of one 
node. But my efforts are directed to the cross-instance usage of a 
monitoring data. As an example, it may be useful for sharding.
Also, I guess for an user is essential to think that if he changed a 
name of any object he also would change queries and reset monitoring 
data, related on this object.

-- 
regards,
Andrey Lepikhov
Postgres Professional



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: [RFC] building postgres with meson
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Accommodate startup process in a separate ProcState array slot instead of in MaxBackends slots.