Re: Upgrade issue (again).

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Upgrade issue (again).
Date: 2001-05-16 23:34:37
Message-ID: 1093.990056077@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> I am loathe to even bring this up, but with two messages today about
>> it, I am going to be short and sweet:
>>
>> We don't have a reasonable upgrade path.

This is one of many, many things that need work. It happens to be a
thing that requires a *lot* of work for, well, not so much payback
(certainly not a benefit you'd get every day you use Postgres).
Not to mention that it's a lot of pretty boring work.

So, personally, there are many other things that I will get to before
I worry about this. Sorry that my priorities don't square with yours,
but that's how it is. I'm not standing in the way of someone else
taking up the problem ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2001-05-17 02:00:14 RE: Configurable path to look up dynamic libraries
Previous Message Tom Lane 2001-05-16 23:06:48 Re: Re: Queries across multiple databases (was: SELECT from a table in another database).