From: | "John Smith" <megs4ml(at)hotmail(dot)com> |
---|---|
To: | pgsql-general(at)hub(dot)org |
Subject: | suggestions on vacuum |
Date: | 1998-09-10 05:20:48 |
Message-ID: | 19980910122049.13479.qmail@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If we are running critical applications that need to have all time
access(select,insert,delete,update,create,etc...) to a database, what
are my options on running a vacuum? Is this vacuum feature only in
Posgres database or is in all databases? I don't think there is
something like this in Oracle, and if we can't figure out a workaround
we might then need to use other database. Any suggestions? We expect it
to do a lot of transactions and _probably_ will need to run vacuum
daily.
Thanks
- John
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
From | Date | Subject | |
---|---|---|---|
Next Message | Anand Surelia | 1998-09-10 16:03:34 | Foreign Keys |
Previous Message | Sferacarta Software | 1998-09-09 15:29:27 | Re: [GENERAL] primary key |