| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Brian Hirt <bhirt(at)mobygames(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Strange problem when upgrading to 7.2 with pg_upgrade. |
| Date: | 2002-02-22 05:08:28 |
| Message-ID: | 14275.1014354508@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I suspect that pg_upgrade has neglected to make sure the clog is long
>> enough.
> Here is the code that sets the transaction id. Tom, does pg_resetxlog
> handle pg_clog file creation properly?
pg_resetxlog doesn't know a single solitary thing about the clog.
The problem here is that if you're going to move the current xact ID
forward, you need to be prepared to create pages of the clog
accordingly. Or maybe the clog routines need to be less rigid in their
assumptions, but I'm uncomfortable with relaxing their expectations
unless it can be shown that they may fail to cope with cases that
arise in normal system operation. This isn't such a case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-02-22 05:12:55 | Re: Strange problem when upgrading to 7.2 with pg_upgrade. |
| Previous Message | Marc Munro | 2002-02-22 05:07:27 | Re: point in time recovery and moving datafiles online |