From: Dimitri Fontaine <dfontaine@hi-media.com>
To: Jesper Krogh <jesper@krogh.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: Message queue table - strange performance drop with changing limit size.
Date: Sat, 02 Jan 2010 13:25:14 +0100
Message-ID: <m2hbr4y9qt.fsf@hi-media.com> (raw)
In-Reply-To: <4B3DE11B.1010708@krogh.cc>
References: <4B3DE11B.1010708@krogh.cc>
Jesper Krogh <jesper@krogh.cc> writes:
> I have a "message queue" table, that contains in the order of 1-10m
> "messages". It is implemented using TheSchwartz:
> http://search.cpan.org/~bradfitz/TheSchwartz-1.07/lib/TheSchwartz.pm
One way to approach queueing efficiently with PostgreSQL is to rely on
PGQ. New upcoming 3.0 version (alpha1 has been released) contains the
basics for having cooperative consumers, stable version (2.1.10) only
allows multiple consumers to all do the same work (think replication).
http://wiki.postgresql.org/wiki/Skytoolshttp://wiki.postgresql.org/wiki/PGQ_Tutorial
Regards,
--
dim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dfontaine@hi-media.com, jesper@krogh.cc
Subject: Re: Message queue table - strange performance drop with changing limit size.
In-Reply-To: <m2hbr4y9qt.fsf@hi-media.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox