From: Nicolai Tufar <ntufar@pisem.net>
To: raymond.siebert@mobilcom.de
To: simon@2ndquadrant.com
Cc: pgsql-hackers-pitr@postgresql.org
Subject: Re: Archival API
Date: Thu, 26 Feb 2004 23:08:32 +0200
Message-ID: <000001c3fcac$b3e2b720$6400a8c0@ntufar> (raw)
In-Reply-To: <OF3F4D8087.7AF8F6C1-ONC1256E46.00373007-C1256E46.003BE191@mobilcom.de>
-----Original Message-----
From: pgsql-hackers-pitr-owner@postgresql.org
[mailto:pgsql-hackers-pitr-owner@postgresql.org] On Behalf Of
raymond.siebert@mobilcom.de
> Another idea is an event handling system in database system.
> Sending defined signals to the 'outer world' through an API to a user
> supplied program.
> This user supplied program can later on handle other events in
addition to > backup of WAL logs.
> A fixed classification of events and a defined framework in user
supplied > program is the way to success.
>
> [ ... ]
>
This is the method used in DB2. It is called "user exit". You can
specify
a program or a compiled C code to be run before, after or instead of
a specific event.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers-pitr@postgresql.org
Cc: ntufar@pisem.net, raymond.siebert@mobilcom.de, simon@2ndquadrant.com
Subject: Re: Archival API
In-Reply-To: <000001c3fcac$b3e2b720$6400a8c0@ntufar>
References: <OF3F4D8087.7AF8F6C1-ONC1256E46.00373007-C1256E46.003BE191@mobilcom.de> <000001c3fcac$b3e2b720$6400a8c0@ntufar>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox