| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Jason Harvey <jason(at)reddit(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers(at)postgresql(dot)org, "Tharakan, Robins" <tharar(at)amazon(dot)com> |
| Subject: | Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load |
| Date: | 2022-07-05 16:59:42 |
| Message-ID: | 1973418.1657040382@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> This patch has been applied back to 9.6 and will appear in the next
> minor release.
I have just discovered that this patch broke pg_upgrade's ability
to upgrade from 8.4:
$ pg_upgrade -b ~/version84/bin -d ...
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
The source cluster lacks some required control information:
latest checkpoint oldestXID
Cannot continue without required control information, terminating
Failure, exiting
Sure enough, 8.4's pg_controldata doesn't print anything about
oldestXID, because that info wasn't there then.
Given the lack of field complaints, it's probably not worth trying
to do anything to restore that capability. But we really ought to
update pg_upgrade's code and docs in pre-v15 branches to say that
the minimum supported source version is 9.0.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-07-05 17:02:38 | Re: How to upgrade postgres version 8 to 13 |
| Previous Message | shashidhar Reddy | 2022-07-05 16:54:30 | How to upgrade postgres version 8 to 13 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-05 17:07:48 | Re: pg_upgrade (12->14) fails on aggregate |
| Previous Message | Nathan Bossart | 2022-07-05 16:58:38 | Re: avoid multiple hard links to same WAL file after a crash |