Re: [PATCH] Detect escape of ErrorContextCallback stack pointers (and from PG_TRY() )

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: [PATCH] Detect escape of ErrorContextCallback stack pointers (and from PG_TRY() )
Дата
Msg-id CAMsr+YGMZG6SrF6NpTaCCjktPQzmauCVrD_6CoOOvLwMRWacsA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Detect escape of ErrorContextCallback stack pointers (and from PG_TRY() )  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: [PATCH] Detect escape of ErrorContextCallback stack pointers (and from PG_TRY() )  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения
On Fri, 4 Sep 2020 at 14:55, Craig Ringer <craig@2ndquadrant.com> wrote:
 

Example here:


So I find that actually, the __attribute__((callback(fn)) approach is unnecessary for the purpose proposed.



I still think we should be looking at tidying up the error contexts API, but it's easy enough for extensions to provide a wrapper over it, so that's not a big deal really.

I will submit my docs patches separately to ensure they get some attention, and I'll experiment with llvm threadsafety annotations / capabilities.




--
 Craig Ringer                   http://www.2ndQuadrant.com/
 2ndQuadrant - PostgreSQL Solutions for the Enterprise

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

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: Resetting spilled txn statistics in pg_stat_replication
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Transactions involving multiple postgres foreign servers, take 2