From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Diogo Biazus" <diogob(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: xlog viewer proposal |
Date: | 2006-06-22 17:00:10 |
Message-ID: | 36e682920606221000j5aeba2atafad3f7a6afaaef4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/22/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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 | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Lukas Smith | 2006-06-22 17:01:38 | Re: vacuum, performance, and MVCC |
Previous Message | Lukas Smith | 2006-06-22 16:58:14 | Re: vacuum, performance, and MVCC |