<[EMAIL PROTECTED]> 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: ot
Hmm i do the below daily to this table. And this is pgsql 7.3
~~~
BEGIN WORK;
INSERT INTO archives.site_search SELECT * from public.site_search;
COMMIT;
TRUNCATE TABLE public.site_search;
~~
and then it is VACUMMED within 24 hrs.
The table public.site_sea
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I assume this is 7.2.X. I know this is fixed in 7.3.1 but I am not sure
> what release we fixed it in. The HISTORY file doesn't have a specific
> mention of the fix. It is not something to be worried about, as I
> remember.
Mmm, I'm not sure. The kno
I assume this is 7.2.X. I know this is fixed in 7.3.1 but I am not sure
what release we fixed it in. The HISTORY file doesn't have a specific
mention of the fix. It is not something to be worried about, as I
remember.
---
I get the following messages while vacuuming
is there anything alarming?
regds
mallah.
On Saturday 25 January 2003 07:11 am, you wrote:
> SET autocommit TO 'on';VACUUM ANALYZE
> WARNING: Rel site_search: Uninitialized page 1 - fixing
> WARNING: Rel site_search: Uninitialized page 2 - fixing
