<div dir="ltr"><div><div><div>Many thanks for all the answers !<br></div>The new version (2.6) is way more stable than 2.3 regarding postgis table.<br></div>I'll do some torture test and submit tickets if I find any problem.<br></div>Cheers,<br>Rémi-C<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-19 13:31 GMT+01:00 George Silva <span dir="ltr"><<a href="mailto:georger.silva@gmail.com" target="_blank">georger.silva@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>I also have a lot of experience with a large number of users (around 15) editing a central database with PostGIS. No problems there.<br><br></div>Remi, the development time for this would be around a day. If you wish to outsource that job, I have some experience with QGIS Plugins and I could develop that for you.<br><br></div>George<br></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Mon, Jan 19, 2015 at 10:29 AM, Bernhard Ströbl <span dir="ltr"><<a href="mailto:bernhard.stroebl@jena.de" target="_blank">bernhard.stroebl@jena.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Andreas,<br>
<br>
I do not think that multi-core rendering is the issue here as Remi mentions to have experienced crashes since QGIS 1.8.<br>
<br>
Remi,<br>
I am using QGIS with Postgres/PostGIS with some dozens of users on a central database _without_ any issues in QGIS (except the multi-core issue Andreas mentioned). So do share your problems together with relevent parts of your data base so they can beanalyzed.<br>
<br>
Bernhard<br>
<br>
Am 19.01.2015 13:19, schrieb Andreas Neumann:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Hi Remi,<br>
<br>
Regarding crashes with Postgis: do you have multithreading with a lot of<br>
CPU cores active? I am experiencing crashes if more than 2 cores are<br>
active. Try limiting to 2 CPU cores and see if this helps.<br>
<br>
Still trying to investigate this issue with the devs.<br>
<br>
Besides the above issue, editing with Postgis works stable for me -<br>
certainly not as many crashes as you say you have.<br>
<br>
Please do not ignore the crashes but try to report them so that the devs<br>
can do something about it.<br>
<br>
Andreas<br>
<br>
On 19.01.2015 11:57, Rémi Cura wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
I think a more global solution is possible.<br>
After all when you load a postgis layer in qgis, if somebody else<br>
changes it, the view is not refreshed, which is annoying (and<br>
sometimes dangerous because you may edit old data).<br>
<br>
It would be easy to ad this (which would also work for my case) using<br>
the LISTEN / NOTIFY feature of postgres.<br>
<br>
Basically when selecting a table as a new qgis layer, you<br>
automatically add a triger to it.<br>
The trigger will be fired at any change (create/delete/update).<br>
The trigger would simply send a message to qgis via NOTIFY.<br>
example : "NOTIFY qgis_change_XXXX ;", where XXXX is a unique id.<br>
Of course qgis would be listening, which is very simple in python<br>
(import psycopg2;<br>
conn = psycopg.connect(my_database_<u></u>string)<br>
conn.autocommit(1)<br>
curs = conn.cursor()<br>
curs.execute("LISTEN qgis_change_XXXX;"))<br>
<br>
Of course one would need a mechanism to remove this trigger when not<br></div></div>
necessary (for instance, name the channel "qgis_change_/time_stamp/",<span><br>
delete channel too old automatically, and change channel periodically<br>
(20 in for instance)).<br>
<br>
I don't know if from a security point of view it would be possibe<br>
tough (would require the permission to create a trigger).<br>
I don't know if typical qgis user have the right to create trigger on<br>
database they use.<br>
<br>
I use a lot of different version of QGIS and I can guarantee at least<br>
a dozen crash a day with version 1.8 to 2.3,<br>
plus pending transaction with postgis whenever the crash occurs.<br>
I'm installing 2.6 to see if postgis layers are less fragile right now ^^<br>
<br>
Cheers,<br>
Rémi-C<br>
<br>
2015-01-19 11:29 GMT+01:00 Martin Dobias <<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a><br></span>
<mailto:<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a>>>:<span><br>
<br>
I see - indeed QGIS would need to do quite some database<br>
inspection to understand that layer A and layer B are related.<br>
This should be however also easy to address in a custom plugin.<br>
<br>
It is surprising to me that you say PostGIS layers are fragile in<br>
QGIS - they are very commonly used by lots of people and we<br>
haven't heard about crashes in the issue tracker. If you do<br>
experience crashes please consider filing reports on <a href="http://hub.qgis.org" target="_blank">hub.qgis.org</a><br></span>
<<a href="http://hub.qgis.org" target="_blank">http://hub.qgis.org</a>> with instructions on how to replicate them.<span><br>
<br>
Regards<br>
Martin<br>
<br>
<br>
On Mon, Jan 19, 2015 at 5:18 PM, Rémi Cura <<a href="mailto:remi.cura@gmail.com" target="_blank">remi.cura@gmail.com</a><br></span><span>
<mailto:<a href="mailto:remi.cura@gmail.com" target="_blank">remi.cura@gmail.com</a>>> wrote:<br>
<br>
Thanks Martin,<br>
one day to several days feel like a very reasonnable order of<br>
magnitude.<br>
<br>
QGis is not refreshing the view because when editing layer A<br>
the postgis data base automatically also edit layer B.<br>
I don't think qgis has a mechanism of tracking dbchanges (it<br>
would be possible tough).<br>
Morevover PostGIS layer are still "fragile" in qgis (crashes<br>
often).<br>
<br>
Thanks for the help,<br>
Cheers<br>
Rémi-C<br>
<br>
2015-01-19 10:56 GMT+01:00 Martin Dobias <<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a><br></span>
<mailto:<a href="mailto:wonder.sk@gmail.com" target="_blank">wonder.sk@gmail.com</a>>>:<span><br>
<br>
Hi Remi<br>
<br>
Such plugin should be quite easy to write - I would assume<br>
up to one day of work for an experienced pyqgis developer.<br>
For a newcomer it may take few more days to get familiar<br>
with the API, tools, environment and so on.<br>
<br>
For the refresh of rendering after geometry editing - that<br>
should work out of the box and I would consider it a bug<br>
if it does not.<br>
<br>
Regards<br>
Martin<br>
<br>
<br>
On Mon, Jan 19, 2015 at 3:16 PM, Rémi Cura<br></span><span>
<<a href="mailto:remi.cura@gmail.com" target="_blank">remi.cura@gmail.com</a> <mailto:<a href="mailto:remi.cura@gmail.com" target="_blank">remi.cura@gmail.com</a>>> wrote:<br>
<br>
Hello dear list.<br>
I'm usually active on the postgis or postgres list,<br>
but today I would like to ask a question regarding dev<br>
time.<br>
<br>
In your opinion,<br>
How much time would be needed to write a plugin for<br>
multiple versions of qgis (2.2 to current 2.6) doing 3<br>
simple things :<br>
- auto commit the edition of geometry when in edition<br>
mode (no need to click on save changes each time)<br>
- force refresh of rendering after edition of a geometry<br>
- every camera changes (zoom or position), send a sql<br>
query containing user name and geometry of view (a<br>
rectangle in wkt for instance).<br>
<br>
I can estimate this at my poor qgis-dev level, but I<br>
would like to have the timing for an expert qgis dev.<br>
<br>
Many thanks,<br>
<br>
Remi-C<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br></span>
<mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></blockquote>
<br>
<br>
__________ Information from ESET Mail Security, version of virus signature database 11036 (20150119) __________<br>
<br>
The message was checked by ESET Mail Security.<br>
<a href="http://www.eset.com" target="_blank">http://www.eset.com</a><div><div><br>
<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr">George R. C. Silva<br>SIGMA Consultoria<div>----------------------------<br><div><a href="http://www.consultoriasigma.com.br/" target="_blank">http://www.consultoriasigma.com.br/</a><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%"></div><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%"></div><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%"></div></div></div></div></div>
</font></span></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div>