| From: | "Steve Wolfe" <nw(at)codon(dot)com> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Upgrade Procedures |
| Date: | 2003-01-03 17:22:13 |
| Message-ID: | 010c01c2b34c$c45ab300$88693fd1@WEASEL |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> 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?
It can be a pain in the butt, but I'm glad that it's done that way. I'd
rather take a small bite up front rather than have the development team
incorporate backwards-compatibility, which even if it COULD be done, would
probably hinder development much more than would be prudent.
steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hernan Salvarezza | 2003-01-03 18:22:08 | Re: Pgadmin II |
| Previous Message | Gaetano Mendola | 2003-01-03 17:22:00 | Re: Vacuuming and re-indexing (was Re: Vacuum meaning) |