[Qgis-user] Incredibly slow attribute view/access from postgresv3.16

Andrew Hughes ahhughes at gmail.com
Wed Oct 6 00:21:35 PDT 2021


Thanks Bernhard,

I'm afraid we are quite well indexed. I'd also expect slow performance on
the map rendering if that were the problem.

Unless of course there is some client side data caching from postgres that
I am not aware of?

Thank you & Cheers,
Andrew

On Wed, 6 Oct 2021 at 16:26, Bernhard Ströbl <bernhard.stroebl at jena.de>
wrote:

> Hi,
> just a few ideas: Do you have a spatial index on the table?
> I have no clue how QGIS handles the attribute table (loading all
> datasets in the first place and then select or else) maybe editing this
> many features is better done directly on the DB?
>
> Bernhard
>
> Am 05.10.2021 um 23:51 schrieb Andrew Hughes:
> > Hi All,
> >
> > Just to get this out the way... *I don't believe this is a problem with
> > the primary key or its index. *
> >
> > I have a postgis datasource with approx 3 million features (road
> > segments). Yep, lot-a-data.
> >
> > The rendering performance is ok & visible @ 1:50,000+ . Takes a few
> > seconds but hey, it's a lot of data and certainly not disappointing.
> >
> > However, severe performance problems are seen whenever I am trying to
> > work with anything related to attribution, such as "Open Attribute
> > Table" or "modify the selected features or all attributes
> > simultaneously". We're talking around 10 minutes of "/Not Responding/".
> >
> > Note: I have altered the QGIS "/Settings -> Options -> Data Sources ->
> > Feature Attributes and Tables/"    so that "/Show selected features/" is
> > now the default attribute table behaviour. So _hopefully_, this doesn't
> > attempt to load all 3million features.
> >
> > Can anyone offer any guidance as to what I might be able to do to track
> > down this issue (or just fix it)? For reference, we are trying to put
> > together a simple editor that will allow a user to browse, select (road
> > segment) features, and edit a single text attribute value on all
> > selected features only. Fairly simple, but the UI elements we need
> > appear to be in a world of pain.
> >
> > Thanks in advance,
> > Andrew
> >
> >
> >
> > _______________________________________________
> > Qgis-user mailing list
> > Qgis-user at lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >
> >
> >
> >
> > __________ Information from ESET Mail Security, version of virus
> signature database 24076 (20211005) __________
> >
> > The message was checked by ESET Mail Security.
> > http://www.eset.com
> >
>
>
>
>
> __________ Information from ESET Mail Security, version of virus signature
> database 24078 (20211006) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20211006/25f7f727/attachment.html>


More information about the Qgis-user mailing list