RE: [HACKERS] Open 6.5 items
От | Hiroshi Inoue |
---|---|
Тема | RE: [HACKERS] Open 6.5 items |
Дата | |
Msg-id | 001601beab2a$c12d4c20$2801007e@cadzone.tpf.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] Open 6.5 items (Bruce Momjian <maillist@candle.pha.pa.us>) |
Ответы |
Re: [HACKERS] Open 6.5 items
|
Список | pgsql-hackers |
> > > > I thought we decided that file descriptors are kept by > backends, and are > > > still accessable while new backends don't see the files. Correct? > > > > > > > Yes,other backends could write to unliked files which would be > > vanished before long. > > I think it's more secure to truncate useless segments to size 0 > > than unlinking the segments though vacuum would never remove > > useless segments. > > If you truncate, other backends will see the data gone, and will be > writing into the middle of an empty file. Better to remove. > I couldn't explain more because of my poor English,sorry. But my test case usually causes backend abort. My test case isWhile 1 or more sessions frequently insert/update a table,vacuum the table. After vacuum, those sessions abort with message ERROR: cannot open segment .. of relation ... This ERROR finally causes spinlock freeze as I reported in a posting [HACKERS] spinlock freeze ?(Re: INSERT/UPDATE waiting (another example)). Comments ? Thanks. Hiroshi Inoue Inoue@tpf.co.jp
В списке pgsql-hackers по дате отправления: