RE: Copy data to DSA area
От | Ideriha, Takeshi |
---|---|
Тема | RE: Copy data to DSA area |
Дата | |
Msg-id | 4E72940DA2BF16479384A86D54D0988A7DB4FB71@G01JPEXMBKW04 обсуждение исходный текст |
Ответ на | Re: Copy data to DSA area (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
RE: Copy data to DSA area
|
Список | pgsql-hackers |
Hi, Thomas >-----Original Message----- >From: Thomas Munro [mailto:thomas.munro@gmail.com] >Subject: Re: Copy data to DSA area > >On Wed, May 8, 2019 at 5:29 PM Ideriha, Takeshi <ideriha.takeshi@jp.fujitsu.com> >wrote: >> >From: Ideriha, Takeshi [mailto:ideriha.takeshi@jp.fujitsu.com] >> >Sent: Friday, April 26, 2019 11:50 PM Well, after developing PoC, I >> >realized that this PoC doesn't solve the local process is crashed >> >before the context becomes shared because local process keeps track >> >of pointer to chunks. >> >Maybe all of you have already noticed and pointed out this case :) So >> >it needs another work but this poc is a good step for me to advance more. >> >> I think the point to prevent memory leak is allocating memory and >> storing its address into a structure at the same time. This structure >> should be trackable from other process. > >I'm not sure that it's necessarily wrong to keep tracking information in private memory. >If any backend crashes, the postmaster will terminate all backends and reinitialise >everything anyway, because shared memory might be corrupted. Thank you very much for the clarification. I haven't looked into reinitialize sequence so much. I checked CreateSharedMemoryAndSemaphores is called again and shared memory gets initialized. So I'm going to put keep tracking information in private memory and send a patch. Regards, Takeshi Ideriha
В списке pgsql-hackers по дате отправления: