| From: | "Sean Davis" <sdavis2(at)mail(dot)nih(dot)gov> |
|---|---|
| To: | messias <messias(at)fw(dot)hu> |
| Cc: | "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Monitoring new records |
| Date: | 2008-02-29 13:00:15 |
| Message-ID: | 264855a00802290500n8aa94b5o8eedd469b6c3eb1e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
2008/2/29 messias <messias(at)fw(dot)hu>:
> --- Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com> wrote (2008.02.29
> 00:38:30): ---
>
>
>
>
> > On 29/02/2008, messias <messias(at)fw(dot)hu> wrote:
>
> > > be filled by a trigger. The client would read from that queue
> table,
>
> > > and delete the readed data.
>
> >
>
> >
>
> > > I think this solution can work with only one client.
>
> > I guess it depends on how you define "client"
>
>
>
> My clients would be a C++ application, and they have to monitor an
>
> event table. The events are comming from for example a fire alarm
>
> system.
Then, you probably want to look at the LISTEN...NOTIFY system. Check
the documentation for more details.
Sean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Cederstrand | 2008-02-29 15:25:42 | Check existence of combination in an M.N relation |
| Previous Message | messias | 2008-02-29 12:16:00 | Re: Re: Monitoring new records |