| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Queues Problem |
| Date: | 2010-06-08 22:29:39 |
| Message-ID: | AANLkTilE5i0WY9gAAYBAVmyG05g_0BFGpmG2ON68Rp61@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 8, 2010 at 2:01 PM, uaca man <uacaman(at)gmail(dot)com> wrote:
>> You will have to write your code to be more event
>>driven, and make the web server just generate requests and view the
>>results where they are stored.
>
> What do you mean? That is what I think I am trying to do. No?
You have work you need done. You want to send that work to some
worker (a cron job or never-ending loop in your description) to do the
work and get back an answer either directly or posted to some place
(the database). Seems to me like gearman and or AMQP would be ideal
solutions, and you can then have as many workers as you want and not
worry about contention of querying for the next job in the table which
inherently requires some form of locking.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Landscheidt | 2010-06-09 00:26:42 | Re: Some insight on the proper SQL would be appreciated |
| Previous Message | Massa, Harald Armin | 2010-06-08 21:07:51 | Re: What does PGDG mean, in the Postgres YUM repositories? |