Re: Postgres not using index on views

From: Thomas Kellerer <shammat(at)gmx(dot)net>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres not using index on views
Date: 2020-04-07 09:24:01
Message-ID: 24349fc1-8245-443e-61e7-f9f86081e551@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> RV>> It simply is the way the application stores the data. For Oracle
> we are storing in XML and JSON format, for postgres, due do
> limitations of XML api, we are storing in VARCHAR.

Why not use JSON in Postgres then?
Postgres' JSON functions are at least as powerful as Oracle's (if not better in a lot of areas).

Would be interesting to see what XML function/feature from Oracle you can't replicate/migrate to Postgres.

Another option might be to upgrade to Postgres 12 and define those columns as generated columns as part of the table, rather than a view.
Then you only pay the performance penalty of the extracValueJS() function when you update the table, not for every select.

Thomas

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Christofides 2020-04-07 10:20:41 Re: slow query
Previous Message Thomas Kellerer 2020-04-07 09:18:04 Re: Postgres not using index on views