From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Open 6.5 items |
Date: | 1999-05-31 06:14:42 |
Message-ID: | 199905310614.CAA11761@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I couldn't explain more because of my poor English,sorry.
>
> But my test case usually causes backend abort.
> My test case is
> While 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 ?
OK, I buy that. How will truncate fix things? Isn't that going to be
strange too. Hard to imagine how we are going to modify these things.
I am now leaning to the truncate option, especially considering that
usually only the last segment is going to be truncated.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Samersoff | 1999-05-31 07:34:59 | Re: [HACKERS] egcs experimentation results |
Previous Message | Hiroshi Inoue | 1999-05-31 05:59:33 | RE: [HACKERS] Open 6.5 items |