| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Diogo Biazus" <diogob(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: xlog viewer proposal |
| Date: | 2006-06-22 16:37:27 |
| Message-ID: | 898.1150994247@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Diogo Biazus" <diogob(at)gmail(dot)com> writes:
> The idea I've been discussing with Simon Riggs is to create a set of
> functions that can be called from within the database.
I'd question that at the very start. I don't see any strong reason to
do it that way, and as you admit further down 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.
I would suggest building the xlog-reader as a separate program, not part
of the backend. It would be useful to have options to (eg) translate
table OIDs to table names, which would require a connection to the
database, but this should be an *option* not an essential condition.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-06-22 16:41:36 | Re: vacuum, performance, and MVCC |
| Previous Message | Mark Woodward | 2006-06-22 16:33:52 | Re: vacuum, performance, and MVCC |