Nigel J. Andrews wrote:
> > > The reason that it needs to be rewritten in C is that it needs access to
> > > internal stuff that the backend doesn't expose. (For example, the
> > > transaction counter, end-of-WAL pointer, etc.) I don't think Perl would
> > > offer anything except creating an entirely new dependency for Postgres.
> > > Also, C code would be easier to keep in sync with the backend code that
> > > accesses the same stuff.
> > True, but doing all that text manipulation is C is going to be very hard
> > to do and maintain.
> What about using embedded perl? I've never done it before but the mention of it
> in manpages has flashed past my eyes a couple of times so I know it's possible.
> Did the discuss decide on what was required for this. Last I noticed was that
> there was a distinction being made between system and user tables but I don't
> recall seeing a 'requirements' summary.
My guess is that we could do it in Perl, and call some C programs as
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-general by date
|Next:||From: Ron Johnson||Date: 2003-09-27 22:11:20|
|Subject: Rewriting pg_upgrade (was Re: State of Beta 2)|
|Previous:||From: Nigel J. Andrews||Date: 2003-09-27 21:50:18|
|Subject: Re: State of Beta 2|