From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Vadim Mikheev <vadim(at)krs(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, t-ishii(at)sra(dot)co(dot)jp, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Open 6.5 items |
Date: | 1999-06-04 14:37:19 |
Message-ID: | 199906041437.KAA15062@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> >
> > Hiroshi wrote:
> >
> > 2.
> > > spinlock io_in_progress_lock of a buffer page is not
> > > released by operations called by elog() such as
> > > ProcReleaseSpins(),ResetBufferPool() etc.
> >
> > I tried to fix this before 6.4 but without success (don't
> > remember why).
> >
>
> This is not in my must-fix-for-6.5 lists.
> For the present this is caused by other bugs not by bufmgr/smgr itself
> and an easy fix may introduce other bugs.
>
>
> And on segmented relations.
>
> Ole Gjerde who provided the patch for current implementation of
> mdtruncate() sayz.
> "First, please reverse my patch to mdtruncate() in md.c as soon as
> possible. It does not work properly in some cases."
>
> I also recommend to reverse his patch to mdtruncate().
>
> Though we could not shrink segmented relations by old implementation
> the result by vacuum would never be inconsistent(?).
>
> I think we don't have enough time to fix this.
So what do we put in its place when we reverse out the patch?
--
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 | Tom Lane | 1999-06-04 14:47:29 | Re: [HACKERS] Priorities for 6.6 |
Previous Message | Bruce Momjian | 1999-06-04 14:15:31 | Re: [HACKERS] Open 6.5 items |