Обсуждение: vacuum warnings with pgsql 7.3.3
Hi, These warnings still come under some mysterious circumstances with PostgreSQL 7.3.3 . is it worth investigating , if yes i will try to get more details . If no i will ignore it for the time being. Regds Mallah. WARNING: Rel site_search: Uninitialized page 1 - fixing WARNING: Rel site_search: Uninitialized page 2 - fixing WARNING: Rel site_search: Uninitialized page 3 - fixing WARNING: Rel site_search: Uninitialized page 4 - fixing WARNING: Rel site_search: Uninitialized page 5 - fixing WARNING: Rel site_search: Uninitialized page 6 - fixing WARNING: Rel site_search: Uninitialized page 7 - fixing WARNING: Rel site_search: Uninitialized page 8 - fixing WARNING: Rel site_search: Uninitialized page 9 - fixing WARNING: Rel site_search: Uninitialized page 10 - fixing WARNING: Rel site_search: Uninitialized page 11 - fixing WARNING: Rel site_search: Uninitialized page 12 - fixing WARNING: Rel site_search: Uninitialized page 13 - fixing WARNING: Rel site_search: Uninitialized page 14 - fixing WARNING: Rel site_search: Uninitialized page 15 - fixing WARNING: Rel site_search: Uninitialized page 16 - fixing WARNING: Rel site_search: Uninitialized page 17 - fixing WARNING: Rel site_search: Uninitialized page 18 - fixing WARNING: Rel site_search: Uninitialized page 19 - fixing WARNING: Rel site_search: Uninitialized page 20 - fixing -- Rajesh Kumar Mallah, Project Manager (Development) Infocom Network Limited, New Delhi phone: +91(11)6152172 (221) (L) ,9811255597 (M) Visit http://www.trade-india.com , India's Leading B2B eMarketplace.
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.
regards, tom lane
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