Re: [HACKERS] PG_UPGRADE status

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] PG_UPGRADE status
Date: 1999-09-09 15:51:09
Message-ID: 37D7D76D.591CF9F1@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> At the end of pg_upgrade, there are the lines:
>
> mv -f $OLDDIR/pg_log data
> mv -f $OLDDIR/pg_variable data
>
> echo "You may remove the $OLDDIR directory with 'rm -r $OLDDIR'."
> exit 0
>
> This is used to get the proper transaction status into the new
> installation. Is the VACUUM added to pg_upgrade necessary?

You know, up until this message I had the mistaken impression that
pg_upgrade was a C program... Boy was I wrong. And no wonder it's
hairy. I should have read the source first -- but nooo, I couldn't do
that. Open mouth, insert foot.

I _am_ contemplating a C version that would do far more than just
upgrades. I'm thinking of a pg_repair utility that could rebuild and
repair the on-disk structures. It would also facilitate database
recovery after a crash -- might be a real bear to do right. Comments?

Lamar Owen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 1999-09-09 15:59:26 Re: [HACKERS] PG_UPGRADE status?
Previous Message Tom Lane 1999-09-09 14:45:36 Re: [HACKERS] Vacuum analyze bug CAUGHT