Re: [HACKERS] Error: dsa_area could not attach to a segment that hasbeen freed

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: [HACKERS] Error: dsa_area could not attach to a segment that hasbeen freed
Дата
Msg-id CAMsr+YHHN0Co37xqe7OUY8j2+QVRW-SAUJyOiw1KGkWqPZ==qQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Error: dsa_area could not attach to a segment that hasbeen freed  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: [HACKERS] Error: dsa_area could not attach to a segment that hasbeen freed  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 20 September 2017 at 17:52, Craig Ringer <craig@2ndquadrant.com> wrote:
On 20 September 2017 at 16:55, Thomas Munro <thomas.munro@enterprisedb.com> wrote:
On Wed, Sep 20, 2017 at 6:14 PM, Gaddam Sai Ram
<gaddamsairam.n@zohocorp.com> wrote:
> Thank you very much! That fixed my issue! :)
> I was in an assumption that pinning the area will increase its lifetime but
> yeah after taking memory context into consideration its working fine!

So far the success rate in confusing people who first try to make
long-lived DSA areas and DSM segments is 100%.  Basically, this is all
designed to ensure automatic cleanup of resources in short-lived
scopes.

90% ;)

I got it working with no significant issues for a long lived segment used to store a pool of shm_mq pairs used for a sort of "connection listener" bgworker. Though I only used DSM+ToC, not DSA.


By the way, dsa.c really needs a cross-reference to shm_toc.c and vice versa. With a hint as to when each is appropriate. 

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: [HACKERS] Error: dsa_area could not attach to a segment that hasbeen freed
Следующее
От: Alexander Korotkov
Дата:
Сообщение: Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions