From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, 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-03 17:24:28 |
Message-ID: | 3756BA4C.16A06A8@krs.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
There are still some bad things, but they are old:
1. elog(NOTICE) in lock manager when locking was not succeeded.
Hope that our recent changes will reduce possibility of this.
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).
3.
> It seems elog(FATAL) doesn't release allocated buffer pages.
> It's OK ?
> AFAIC elog(FATAL) causes proc_exit(0) and proc_exit() doesn't
> call ResetBufferPool().
Seems to me that elog(FATAL) should call siglongjmp(Warn_restart, 1),
like elog(ERROR), but force exit in tcop main loop after
AbortCurrentTransaction(). AbortTransaction() does pretty nice
things like RelationPurgeLocalRelation(false) and DestroyNoNameRels()...
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-03 17:32:15 | Priorities for 6.6 |
Previous Message | Bruce Momjian | 1999-06-03 16:48:07 | Re: [HACKERS] Re: Freezing docs for v6.5 |