Search Postgresql Archives

Re: Processing a work queue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Postgres General <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: Processing a work queue
From: "John D. Burger" <john@xxxxxxxxx>
Date: Mon, 30 Apr 2007 11:42:01 -0400
In-reply-to: <slrnf378jf.2vn3.andrew+nonews@xxxxxxxxxxxxxxxxxxxxxx>
References: <46312973.3010006@xxxxxxxxxxxxxxxxxxxx> <slrnf378jf.2vn3.andrew+nonews@xxxxxxxxxxxxxxxxxxxxxx>

Andrew - Supernews wrote:

Anyone have any ideas on how to handle a work queue?


Advisory locks (userlocks in pre-8.2).

Can someone explain why these are a better fit than whatever locksSELECT FOR UPDATE acquires?


Thanks.


- John D. Burger
  MITRE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Processing a work queue
  - From: Andrew - Supernews
- Re: Processing a work queue
  - From: Merlin Moncure
- Re: Processing a work queue
  - From: Merlin Moncure

References:
- Processing a work queue
  - From: Steve Crawford
- Re: Processing a work queue
  - From: Andrew - Supernews

Prev by Date: Server crash on postgresql 8.2.4 with tsearch2
Next by Date: Re: Stemming not working with tsearch2() function
Previous by thread: Re: Processing a work queue
Next by thread: Re: Processing a work queue
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux