Re: xlog viewer proposal - Mailing list pgsql-hackers

From Tom Lane
Subject Re: xlog viewer proposal
Date
Msg-id 1380.1150997375@sss.pgh.pa.us
Whole thread Raw
In response to Re: xlog viewer proposal  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: xlog viewer proposal  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Re: xlog viewer proposal  ("Diogo Biazus" <diogob@gmail.com>)
List pgsql-hackers
"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> I think it should certainly be able to run on it's own, but it
> wouldn't be that hard to extend the functions so that they were usable
> from within the database or vice-versa.

Yes it would.  The most obvious point is that memory management and
error handling conventions inside the backend are quite different from
what you'd expect to employ in a standalone program.  Also the means
you'd use for consulting the system catalogs (in that option to provide
readable names for OIDs) are entirely different.

I think asking for support of both environments is a good way to ensure
that this summer project doesn't get finished :-(
        regards, tom lane


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: vacuum, performance, and MVCC
Next
From: "Mark Woodward"
Date:
Subject: Re: vacuum, performance, and MVCC