| From: | valgog <valgog(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multithreaded queue in PgSQL |
| Date: | 2008-06-11 08:22:59 |
| Message-ID: | 9c3e1218-9930-4e9a-be52-67ca7625e01f@m73g2000hsh.googlegroups.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 10, 1:58 pm, alok(dot)(dot)(dot)(at)yahoo(dot)com (Nikola Milutinovic) wrote:
> > You may find that the PGQ component of skytools is what you want:
> > http://pgfoundry.org/projects/skytools
> > http://skytools.projects.postgresql.org/doc/
> > http://skytools.projects.postgresql.org/doc/pgq-sql.html
>
> Thanks, we will look into it. Still, I am surprised to learn that SQL as such cannot handle it. I do realize that the question is not trivial. Would setting transaction isolation level to SERIALIZABLE help in any way? Would locking of the entire table help in any way?
>
> Nix.
The easiest solution that I have found by now, is to use advisory
lock, so that every thread is waiting until the other has released the
lock.
-- Valentine
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-06-11 08:42:59 | Re: Insert into master table ->" 0 rows affected" -> Hibernate problems |
| Previous Message | Magnus Hagander | 2008-06-11 08:14:40 | Re: [ANNOUNCE] PostgreSQL Software Catalogue |