bricklen wrote: > On Fri, Apr 8, 2011 at 10:01 PM, bricklen <brick...@gmail.com> wrote: > > Update on the status of the steps we took, which were: > > - test on a hot standby by bringing it live, running the script, > > determing the missing clog files, copying them into the live (hot > > standby) pg_clog dir > > > > Now, on the master, copied the same old clog files into the production > > *master*, ran vacuumdb -a -v -F. The step I should have taken on the > > master before the vacuumdb -F would have been to run the > > http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix script to see > > if I was missing any clog files on the master. > > That vacuum freeze step pointed out a clog file, I copied that into > > the master pg_clog dir, ran the aforementioned script. It didn't fail > > on any of the clog files this time, so now I am rerunning the vacuum > > freeze command and hoping like hell it works! > > > > If the current run of the vacuum freeze fails, I'll report back. > > > > Thanks again for everyone's help. > > > > The vacuumdb -a -v F completed successfully this time.
YEA! -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
