| From: | "Nicolai Tufar" <ntufar(at)pisem(dot)net> |
|---|---|
| To: | <raymond(dot)siebert(at)mobilcom(dot)de>, <simon(at)2ndquadrant(dot)com> |
| Cc: | <pgsql-hackers-pitr(at)postgresql(dot)org> |
| Subject: | Re: Archival API |
| Date: | 2004-02-26 21:08:32 |
| Message-ID: | 000001c3fcac$b3e2b720$6400a8c0@ntufar |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-pitr |
-----Original Message-----
From: pgsql-hackers-pitr-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-pitr-owner(at)postgresql(dot)org] On Behalf Of
raymond(dot)siebert(at)mobilcom(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-02-26 21:22:50 | Re: Archival API |
| Previous Message | raymond.siebert | 2004-02-26 10:54:03 | Re: Archival API |