RE: [HACKERS] Open 6.5 items

> -----Original Message-----
> From: root(at)sunpine(dot)krs(dot)ru [mailto:root(at)sunpine(dot)krs(dot)ru]On Behalf Of Vadim
> Mikheev
> Sent: Friday, June 04, 1999 2:24 AM
> To: Tom Lane
> Cc: Hiroshi Inoue; t-ishii(at)sra(dot)co(dot)jp; PostgreSQL-development
> Subject: Re: [HACKERS] Open 6.5 items
>
> Tom Lane wrote:
> >
> > Vadim Mikheev <vadim(at)krs(dot)ru> writes:
> > >> ERROR: Child itemid marked as unused
> > > [ is fixed ]
> >
> > Great! Vadim (also Hiroshi and Tatsuo), how many bugs remain on your
> > must-fix-for-6.5 lists? I was just wondering over in the "Freezing
> > docs" thread whether we had any problems severe enough to justify
> > delaying the release. It sounds like at least one such problem is
> > gone...
>
> No one in mine.
>

[snip]

>
> 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.

Thanks.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp