RE: Is PREPARE of ecpglib thread safe?
От | Matsumura, Ryo |
---|---|
Тема | RE: Is PREPARE of ecpglib thread safe? |
Дата | |
Msg-id | 03040DFF97E6E54E88D3BFEE5F5480F737AC3AD8@G01JPEXMBYT04 обсуждение исходный текст |
Ответ на | Re: Is PREPARE of ecpglib thread safe? (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>) |
Ответы |
Re: Is PREPARE of ecpglib thread safe?
|
Список | pgsql-hackers |
Horiguchi-san Thank you for your comment. > A connection cannot be concurrently used by multiple threads so > the programmer must guard connections using mutex [1] or > friends. If it is done by a single mutex (I suppose it is > common.), there's no race condition also on the prepared > statement storage. I'm not sure it is explicitly aimed but I > suppose that there's no problem in a common usage of the library. I understand it, but current scope of StatementCache and DeclareStatementList seems not to be limitted within each connection, isn't it? Therefore, I thought the operation on them must be thread safe. For example, scope of DescriptorList in descriptor.c is within thread (not connection) by using pthread_getspecific/ pthread_setspecific(). Regards Ryo Matsumura
В списке pgsql-hackers по дате отправления: