| From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
|---|---|
| To: | Andrew Snow <als(at)giskard(dot)fl(dot)net(dot)au> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgresqlism & Vacuum? |
| Date: | 2000-04-14 15:34:10 |
| Message-ID: | 38F73A72.88CDAD95@austin.rr.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrew Snow wrote:
>
> On Fri, 14 Apr 2000, Thomas wrote:
>
> > For large 24x7 installations, it's impossible to vacuum nightly because when
> > postgresql is vacuuming the table is locked up, to the end-user the database
> > has already hung.
>
> That's right. I complained about this in a discussion with a Postgresql
> developer, who assured me they were working towards a fix. I really don't
> care whether the vacuuming is fixed so that it does not lock the table
> completely, or that vacuuming becomes say, a once-a-month or less frequent
> operation. For some reason everyone who is used to working with PostgreSQL
> accepts the fact that you have to vacuum nightly - to outsiders it seems
> like a major flaw with the system.
The vacuum requirement is a bummer. After working with pg for 9 months
now, I consider it a major opportunity for improvement. I wish I had the
time...
Regards,
Ed Loehr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen J Lombardo | 2000-04-14 15:58:48 | Re: Postgresqlism & Vacuum? |
| Previous Message | Ed Loehr | 2000-04-14 15:17:38 | Re: database file size bloat |