Re: [HACKERS] Proper cleanup at backend exit
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] Proper cleanup at backend exit |
Дата | |
Msg-id | 199810020225.WAA23362@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Proper cleanup at backend exit (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
> Bruce Momjian <maillist@candle.pha.pa.us> writes: > >> [ should we work harder to ensure pg_listener entries get cleaned out? ] > > > Seems like we should try and clean them out, especially when the backend > > is doing a normal exit. In a panic exit, we don't need to clean it out. > > OK, I will add some more code to try to cope with the exit-during- > uncommitted-transaction case. > > > We can install something into proc_exit() and shmem_exit() to clean out > > the table. > > The old code inserted the cleanup action into shmem_exit(). Is that the > right list to put it in? I'm not clear on the difference between > shmem_exit and proc_exit lists... proc_exit is triggered on every backend exit. shmem_exit is for postmaster exit, or postmaster shared memory reset. > > > You can have a global variable that installed the pg_listen > > cleaner the first time a notify() is done so as not to install a new > > exit handler for each notify() call. > > That part's already done. Cool. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
В списке pgsql-hackers по дате отправления: