| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Steve Wolfe" <nw(at)codon(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Upgrade Procedures |
| Date: | 2003-01-03 20:48:47 |
| Message-ID: | 11275.1041626927@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Steve Wolfe" <nw(at)codon(dot)com> writes:
>> 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.
This is, um, an ancient topic. See thread "Upgrading rant" now in
progress on pgsql-hackers for the latest rehash of the arguments ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-01-03 23:39:09 | Re: Vacuuming and re-indexing (was Re: Vacuum meaning) |
| Previous Message | Hernan Salvarezza | 2003-01-03 18:22:08 | Re: Pgadmin II |