On 6/22/06, Tom Lane <[EMAIL PROTECTED]> wrote:
it'd make it impossible to use the viewer to work on extracting data from a failed cluster; which is, at least in my mind, one of the primary use-cases for the thing.
While I too see this as something which could be used for this outside the database, I don't think being able to access it from within the system would be bad either.
I would suggest building the xlog-reader as a separate program, not part of the backend.
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. I just don't see it as mutually exclusive. It would be relatively easy to interface it from either side once the core functionality is there. -- Jonah H. Harris, Software Architect | phone: 732.331.1300 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 2nd Floor | [EMAIL PROTECTED] Iselin, New Jersey 08830 | http://www.enterprisedb.com/ ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
