Thanks for your support David and Afsar.
Hi David,
Could you please suggest the resource link to "Add a trigger to the table
to normalize the contents of column1 upon insert and then rewrite your
query to reference the newly created normalized fields." if anything
available. So that it will help
Dear team,
Kindly try to execute the vacuum analyzer on that particular table and
refresh the session and execute the query.
VACUUM (VERBOSE, ANALYZE) tablename;
Regards,
Mohammed Afsar
Database engineer
On Fri, May 22, 2020, 12:30 PM postgann2020 s
wrote:
> Hi Team,
>
> Thanks for your suppo
On Thursday, May 21, 2020, postgann2020 s wrote:
>
> SELECT seq_no+1 INTO pair_seq_no FROM SCHEMA.TABLE WHERE (Column1 like
> '%,sheath--'||cable_seq_id ||',%' or Column1 like 'sheath--'||cable_seq_id
> ||',%' or Column1 like '%,sheath--'||cable_seq_id or
> Column1='sheath--'||cable_seq_id) orde
Hi Team,
Thanks for your support.
Could you please suggest on below query.
EnvironmentPostgreSQL: 9.5.15
Postgis: 2.2.7
The table contains GIS data which is fiber data(underground routes).
We are using the below query inside the proc which is taking a long time to
complete.
**
Hi Team,
Thanks for your support.
Could you please suggest on below query.
We have multiple long procs that are having 100s of data validations and
currently we have written as below.
***
if (SELECT 1 FROM SCHEMA.TABLE WHERE column=data AND column=data) then
statements
etc..
*
Hi Team,
Thanks for your support.
We are using below environment:
Application :
Programming Language : JAVA
Geoserver
Database Stack:
PostgreSQL : 9.5.15
Postgis
We have 3 geoserver queries and are getting some performance issues after
changing the GeoServer queries.I have posted the queries a
