| From: | Ryan Mahoney <ryan(at)paymentalliance(dot)net> |
|---|---|
| To: | Mark <mark(at)ldssingles(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: vacuum and 24/7 uptime |
| Date: | 2001-07-11 16:46:56 |
| Message-ID: | 5.0.2.1.0.20010711174402.03077060@paymentalliance.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
Hi Mark, This is being worked on now. I believe the 7.2 release will have
enable you to run a vacuum with no downtime.
-r
At 03:39 PM 7/11/01 -0600, Mark wrote:
>Is Postgresql ready for 24/7 uptime? Our tests have shown that vacuumdb
>requires downtime, and if one does this nightly as suggested, well, one has
>downtime, 40+ minutes in our case.
>
>My company wants to replace MS SQL Server with PostgreSQL, but we can't
>afford downtime to do database maintenance. Is it possible that we are doing
>something wrong?
>
>What are the plans for future versions of pgsql? Will vacuum be optomized or
>otherwise enhanced to execute more quickly and/or not lock tables?
>
>Thanks,
>
>Mark
>
>PS
>I posted more details to the hackers list.
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://www.postgresql.org/search.mpl
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com)
>Version: 6.0.251 / Virus Database: 124 - Release Date: 4/26/01
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 166 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-11 16:51:59 | Re: Performance tuning for linux, 1GB RAM, dual CPU? |
| Previous Message | Thalis A. Kalfigopoulos | 2001-07-11 16:44:33 | Re: Postgresql revisited. Some questions about the product0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-07-11 17:40:59 | RE: jdbc and unix signals |
| Previous Message | Dave Cramer | 2001-07-11 16:14:58 | RE: JDBC and stored procedures |