RE: [HACKERS] Open 6.5 items - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: [HACKERS] Open 6.5 items
Date
Msg-id 001601beab2a$c12d4c20$2801007e@cadzone.tpf.co.jp
Whole thread Raw
In response to Re: [HACKERS] Open 6.5 items  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Open 6.5 items  (Bruce Momjian <maillist@candle.pha.pa.us>)
List 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 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Open 6.5 items
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Open 6.5 items