Re: VACUUM and transactions in different databases

Hi Bill

 > I don't believe that's the reason.  AFAIK, activity in one database
 > will never block activity in another.

This way I read the documentation.

 > I would suspect that you haven't vacuumed this database in a long time,

I created both databases one hour ago for just testing this behaviour. I
started with two identical tables, each with 5000 rows in both
databases. In db1 I opened a transaction, updated the table and left the
transaction open.

In db2 I updated, inserted and deleted a lot and then tried to vacuum.

 > Can you run a "vacuum
 > full", and does it reclaim the space?

I tried but it hangs.

[root@conni ~]# ps axw|grep postgres
  1746 ?        S      0:00 postgres: writer process
  1747 ?        S      0:00 postgres: stats buffer process
  1748 ?        S      0:00 postgres: stats collector process
  2106 pts/1    S      0:00 su postgres
  2120 pts/1    S+     0:00 psql postgres
  2188 ?        S      0:04 postgres: postgres dummy1 [local] VACUUM waiting
  2200 pts/3    S      0:00 su postgres
  2215 ?        S      0:00 postgres: postgres dummy2 [local] idle in
transaction
  2717 pts/2    R+     0:00 grep postgres

Regards
Conni