| From: | Naomi Walker <nwalker(at)eldocomp(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Upgrade Procedures |
| Date: | 2003-01-03 16:10:31 |
| Message-ID: | 4.2.2.20030103090545.014d97d0@imap.eldocomp.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>The whole "vaccuum" concept is, IMHO, one of the weakest aspects of
>PostgreSQL.
Speaking of which, we love Postgresql, but I am concerned about the fact
that major upgrades require unloading and reloading the database. We are
small enough now, so it is not really a concern. I cannot imagine this
happening with really large database clusters (>50-100gigs).
I know for minor releases, there are upgrade programs to let this happen in
place. Is there any plan for not always having to load and reload in the
future?
----------------------------------------------------------------------------
----------------------------------
Naomi Walker
Eldorado Computing, Inc
Chief Information Officer
nwalker(at)eldocomp(dot)com
602-604-3100 x242
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hernan Salvarezza | 2003-01-03 16:23:14 | Pgadmin II |
| Previous Message | David F. Skoll | 2003-01-03 15:18:46 | Vacuuming and re-indexing (was Re: Vacuum meaning) |