Re: Invalid primary_slot_name triggers warnings in all processes on reload

Поиск
Список
Период
Сортировка
От Chao Li
Тема Re: Invalid primary_slot_name triggers warnings in all processes on reload
Дата
Msg-id A9F6C4EF-FE01-44D5-A583-50CD7A61EED5@gmail.com
обсуждение исходный текст
Ответ на Re: Invalid primary_slot_name triggers warnings in all processes on reload  (Fujii Masao <masao.fujii@gmail.com>)
Ответы Re: Invalid primary_slot_name triggers warnings in all processes on reload
Список pgsql-hackers


On Sep 19, 2025, at 00:48, Fujii Masao <masao.fujii@gmail.com> wrote:

Fujii Masao
<v2-0001-Make-invalid-primary_slot_name-follow-standard-GU.patch>

```
+error:
+ if (elevel == 0)
+ {
+ GUC_check_errdetail("%s", err_msg);
+ if (err_hint != NULL)
+ GUC_check_errhint("%s", err_hint);
+ }
+ else
+ ereport(elevel,
+ (errcode(err_code),
+ errmsg("%s", err_msg),
+ (err_hint != NULL) ? errhint("%s", err_hint) : 0));
+
+ return false;
```

Do we need to free memory pointed by err_msg and err_hint that were allocated from psprintf()? The code comment of psprintf() says caller is responsible for free the memory.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/




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