| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | bricklen <bricklen(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade bug found! |
| Date: | 2011-04-09 02:11:06 |
| Message-ID: | 20110409021106.GJ4548@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
bricklen,
* bricklen (bricklen(at)gmail(dot)com) wrote:
> I looked deeper into our backup archives, and it appears that I do
> have the clog file reference in the error message "DETAIL: Could not
> open file "pg_clog/04BE": No such file or directory."
Great! And there's no file in pg_clog which matches that name (or
exist which are smaller in value), right?
> It exists in an untouched backup directory that I originally made when
> I set up the backup and ran pg_upgrade. I'm not sure if it is from
> version 8.4 or 9.0.2 though. Is it safe to just copy it into my
> production pg_clog dir and restart?
It should be, provided you're not overwriting any files or putting a
clog file in place which is greater than the other clog files in that
directory.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-09 02:12:58 | Re: pgindent |
| Previous Message | bricklen | 2011-04-09 02:01:27 | Re: pg_upgrade bug found! |