Re: SearchSysCacheTuple(Copy)

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SearchSysCacheTuple(Copy)
Date: 2000-11-14 07:26:52
Message-ID: 3A10E93B.9041559E@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > I fixed a few bugs caused by SearchSysCacheTuple()
> > recently. There seems to remain more similar bugs.
>
> Yes, I'm sure there are a lot :-(. We have talked about solving this
> by using some form of reference-counting in the cache, but I don't
> believe anyone's put forward a complete proposal. See for example
> the pghackers thread "Another nasty cache problem" around 30-Jan-2000.
>

Those bugs are pretty serious.
Sometimes they caused ERROR with strange messags.
Sometimes database-wide restart has been caused
by segmentation fault error. Database-wide restart
is pretty serious for any dbms.
And possibly they might have done the wrong thing
silently.
Isn't it practical to replace all susipicious Search
SysCacheTuple() by SearchSysCacheTupleCopy() ?

Regards.
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-14 07:35:44 Re: SearchSysCacheTuple(Copy)
Previous Message Tom Lane 2000-11-14 07:23:43 Re: Shouldn't default multibyte encoding come from template database?