From: | Allan Engelhardt <allane(at)cybaea(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | VACUUM on database with open transaction returns error? |
Date: | 2001-08-13 20:00:42 |
Message-ID: | 3B7831EA.4F3C8309@cybaea.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In one window connect with psql to the database 'test' and execute
test=# begin transaction;
In another window as the postgrs user do
bash-2.04$ vacuumdb -z -a
Vacuuming www
VACUUM
Vacuuming template1
NOTICE: RegisterSharedInvalid: SI buffer overflow
NOTICE: InvalidateSharedInvalid: cache state reset
VACUUM
Vacuuming test
VACUUM
Vacuuming photo
VACUUM
bash-2.04$ vacuumdb -z -a
Vacuuming www
NOTICE: RegisterSharedInvalid: SI buffer overflow
NOTICE: InvalidateSharedInvalid: cache state reset
VACUUM
Vacuuming template1
VACUUM
Vacuuming test
VACUUM
Vacuuming photo
NOTICE: RegisterSharedInvalid: SI buffer overflow
NOTICE: InvalidateSharedInvalid: cache state reset
VACUUM
bash-2.04$ vacuumdb -z -a
Vacuuming www
VACUUM
Vacuuming template1
VACUUM
Vacuuming test
VACUUM
Vacuuming photo
NOTICE: RegisterSharedInvalid: SI buffer overflow
NOTICE: InvalidateSharedInvalid: cache state reset
VACUUM
bash-2.04$
Back in the first window do:
test=# COMMIT ;
NOTICE: InvalidateSharedInvalid: cache state reset
COMMIT
OK, what gives?
1. Should I worry about these messages at all?
2. Is it supported to VACUUM a database with open transactions?
If not: what am I suppoed to do?
3. Why does the NOTICE move around like this?
4. Are there any problems with my transaction in the first window?
Now I'm worried.....
--- Allan.
PostgreSQL 7.1.2-4PGDG on Linux 2.4.7 i686 SMP (glibc 2.2.2-10)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-13 21:46:58 | Re: VACUUM on database with open transaction returns error? |
Previous Message | Adam Kornick | 2001-08-13 19:42:35 | backend closing unexpectedly |