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

Поиск
Список
Период
Сортировка
От Frédéric Yhuel
Тема Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Дата
Msg-id f40c6ac6-1358-4a59-bfd4-ebb7427e7497@dalibo.com
обсуждение исходный текст
Ответ на Re: [BUG] temporary file usage report with extended protocol and unnamed portals  (Sami Imseih <samimseih@gmail.com>)
Ответы Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Список pgsql-hackers

On 4/22/25 19:37, Sami Imseih wrote:
> the patch relies on looking up queryDesc->sourceText inside DropPortal,
> which Tom raised concerns about earlier in the thread [0]

Yes, I think I had misunderstood what Tom said. Thank you for pointing 
that out.

However, is it really unsafe?

In exec_bind_message, the portal's query string comes from a duplicate 
of the original string (see CreateCachedPlan). So we are safe in this case.

In exec_simple_query, the portal is dropped towards the end of this 
function, so we are safe here too.

Am I missing something?



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