| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?! |
| Date: | 2012-06-13 18:43:23 |
| Message-ID: | 20120613184323.GA16165@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 13, 2012 at 02:32:21PM -0400, Bruce Momjian wrote:
> I assume 8.3 vacuumdb did not generate these errors. If it was 8.4 I
> would suggest it was because we don't copy visibility map files from
> pre-9.1 because those were not crash-safe, but 8.3 didn't have
> visibility map files (added in PG 8.4), so 8.3 should have been checking
> the exact same transaction ids as 9.1.
>
> Basically, I can't think of a cause.
yeah, neither can we. but - any other test - even using the same source
of $PGDATA went flawless. I'm tempted to assume it's just a random
glitch in matrix, and just go on.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-06-13 18:55:41 | Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?! |
| Previous Message | Bruce Momjian | 2012-06-13 18:32:21 | Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?! |