| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
| Cc: | PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Standard replication interface? |
| Date: | 2002-08-15 14:53:15 |
| Message-ID: | 871y90cgx0.fsf@klamath.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Sullivan <andrew(at)libertyrms(dot)info> writes:
> On Wed, Aug 14, 2002 at 10:15:32PM -0500, Greg Copeland wrote:
> > Reading about the pgmonitor thread and mention of gborg made me wonder
> > about replication and ready ability to uniformly monitor it. Just as
> > pg_stat* tables exist to allow for statistic gathering and monitoring in
> > a uniform fashion, it occurred to me that a predefined set of views
> > and/or tables for all replication implementations may be worthwhile.
> > That way, no matter what replication method/tool is being used, as long
> > as it conforms to the defined replication interfaces, generic monitoring
> > tools can be used to keep an eye on things.
>
> That sounds like the cart is before the horse.
That's exactly what I was going to say -- I'd prefer that any
interested parties concentrate on producing a *really good*
replication implementation, which might eventually be integrated into
PostgreSQL itself.
Producing a "generic API" for something that really doesn't need
genericity sounds like a waste of time, IMHO.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-15 15:05:07 | Companies involved in development |
| Previous Message | Andrew Sullivan | 2002-08-15 14:47:56 | Re: Standard replication interface? |