Re: [BUG] temporary file usage report with extended protocol and unnamed portals

Поиск
Список
Период
Сортировка
От Sami Imseih
Тема Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Дата
Msg-id CAA5RZ0vsx0HheWTHYuN_61uHKHKHgV-hz5XsYGN-zHHH2t-qNA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUG] temporary file usage report with extended protocol and unnamed portals  (Sami Imseih <samimseih@gmail.com>)
Список pgsql-hackers
> So, It seems to me we are better off just setting debug_query_string
> to NULL in DropPortal, or alternatively why not just log the statement
> automatically at the start of execution whenever we have log_temp_files > 0.
> That will allow us to safely capture the statement to blame for the
> temp files and will cover all cases?

of course we only know about the temp file usage after execution,
so this means we will probably end up with unnecessary
statement logging, so this may not be such a good idea after all.

So this tells me not logging STATEMENT along with log_temp_files is a
better alternative and a statement can be logged with other existing
mechanisms like log_min_duration_statement.

--
Sami Imseih
Amazon Web Services (AWS)



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