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

[Alexandre Neto]

Hi Andrew,

Long story short, the attributes table code is quite old and needs to be
refactored. Unfortunately, it seems that it is a huge a task, that needs
quite an investment and, until now, no one stepped up to fund it.

Meanwhile, I suggest you avoid using table of attributes and it's tools as
much as you can. You already found one workaround, here's a few more:

- don't use the field calculator inside the attributes table, use the one
in QGIS main window toolbar. Much faster.
- don't use the edit multiple features attributes from within the
attributes table, use the one in the editing toolbar.
-if possible, narrow down the size of the table in rows and columns.

The problem with this tools inside the attribute table is that all rows are
loaded before you can open the attribute table, also, if you try to edit a
few, it will try to update all the rows for display (even that you can only
see a subset)

Hope I have helped.

Alexandre Neto
QGIS Support
www.qcooperative.net

A terça, 5/10/2021, 22:53, Andrew Hughes <ahhughes at gmail.com> escreveu:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20211006/e4b73057/attachment.html>