--0-1426878713-1213099109=:28936
Content-Type: text/plain; charset=us-ascii
> 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.
--0-1426878713-1213099109=:28936
Content-Type: text/html; charset=us-ascii
<html><head><style type="text/css"><!-- DIV {margin:0px;}
--></style></head><body><div style="font-family:times new roman, new york,
times, serif;font-size:12pt"><div style="font-family: times new roman,new
york,times,serif; font-size: 12pt;"><div style="font-family: times new
roman,new york,times,serif; font-size: 12pt;">> You may find that the
PGQ component of skytools is what you want:<br>> <a
href="http://pgfoundry.org/projects/skytools"
target="_blank">http://pgfoundry.org/projects/skytools</a><br>>
<a href="http://skytools.projects.postgresql.org/doc/"
target="_blank">http://skytools.projects.postgresql.org/doc/</a><br>>
<a href="http://skytools.projects.postgresql.org/doc/pgq-sql.html"
target="_blank">http://skytools.projects.postgresql.org/doc/pgq-sql.html</a><br>><br><br>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?<br><br>Nix.<br></div></div></div><br>
</body></html>
--0-1426878713-1213099109=:28936--


|