| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: a vulnerability in PostgreSQL |
| Date: | 2002-06-02 06:21:14 |
| Message-ID: | 200206020621.g526LFA14003@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Trond Eivind Glomsrd wrote:
> Postgresql doesn't support upgrades[1], so if we're going to release
> upgrades[2], we'd need the backported fixes for 6.5, 7.0 and 7.1
>
> [1] Not the first time I mention this, is it?
There is now /contrib/pg_upgrade. It has all the things I can think of
for upgrading. Hopefully it can be tested extensively for 7,3 and fully
supported.
If people don't like that it is a shell script, it can be rewritten in
another language, but the basic steps it takes will have to be done no
matter what language it is written in.
However, as I have warned before, an major change from 7.2 to 7,3 could
make it unusable. My point is that it isn't that I haven't tried to
make an upgrade script --- the problem is that making one sometimes is
impossible.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-06-02 06:23:53 | Re: a vulnerability in PostgreSQL |
| Previous Message | Bruce Momjian | 2002-06-02 06:09:25 | Re: Search from newer tuples first, vs older tuples first? |