Hello,
O.k. maybe I am missing something.. but what can I do to make it so a
vacuum full
isn't required? Is this some 7.4 magic that I don't know about?
J
Josh Berkus wrote:
Josh,
Not if it is a vacuum full and you are trying to do an insert. Which is
exactly what
I am talking about. Doing a vacuum full on a table that has had 5.7 million
inserts/updates/deletes during the last 23 hours is going to cause a rather
long vacuum full which in turn will cause a rather long period of
unavailability
of the database.
But if you've set it up correctly in the first place, the vacuum full won't be
necessary.
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@xxxxxxxxxxxxxxxxx - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
