| From: | Chris Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: background triggers? |
| Date: | 2006-05-24 14:44:45 |
| Message-ID: | 60k68b5voi.fsf@dba2.int.libertyrms.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sim Zacks <sim(at)compulab(dot)co(dot)il> writes:
> The reason why the client application would have to wait is because
> the front-end is written in MSAccess. While Windows supports multi
> threading, Access does not support multi threading.
> (Multi threading allows background processing, IYDK)
Well, you *clearly* need to have some sort of "daemon" running in
order to do this.
I expect it will in effect be a LISTEN process that waits for clients
to submit NOTIFY requests.
Even if you don't actually choose to use NOTIFY/LISTEN, per se, you'll
doubtless wind up creating an ad hoc, informally-specified
implementation of part of it...
--
let name="cbbrowne" and tld="ntlug.org" in name ^ "@" ^ tld;;
http://www.ntlug.org/~cbbrowne/unix.html
"Any sufficiently complicated C or Fortran program contains an ad hoc
informally-specified bug-ridden slow implementation of half of Common
Lisp." -- Philip Greenspun
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2006-05-24 14:48:10 | Re: [SQL] (Ab)Using schemas and inheritance |
| Previous Message | Sim Zacks | 2006-05-24 14:04:00 | Re: background triggers? |