On Saturday 05 Jul 2003 7:16 pm, Tom Lane wrote:
> Rajesh Kumar Mallah <mallah@trade-india.com> writes:
> > These warnings still come under some mysterious
> > circumstances with PostgreSQL 7.3.3 .
> >
> > is it worth investigating ,
>
> Yes.
It is the same problem , and below is the reply you gave
few months back i think
=================================================================
<mallah@trade-india.com> writes:
> Hmm i do the below daily to this table. And this is pgsql 7.3
> TRUNCATE TABLE public.site_search;
Drat. Now that I look at it, 7.3 TRUNCATE doesn't send any kind of
relcache inval message, so it's got the same kind of problem that the
nailed-in-cache catalogs do: other backends don't reset their
which-page-to-insert-on pointer.
This is already fixed for 7.4, because in 7.4 TRUNCATE updates the
pg_class entry.
We decided not to backpatch any fix for the system-catalog version
of the problem, because it is purely cosmetic (there is no problem
other than the warning messages). So I guess I think the same about
this version of the problem.
regards, tom lane
======================================================================
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
