Thread: Re: Suggestion to improve query performance of data validation in proc.
Re: Suggestion to improve query performance of data validation in proc.
From
"David G. Johnston"
Date:
You should read through the and the contained linked FAQ - note especially the concept and recommendation for “cross-posting”.
https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics
On Thursday, May 21, 2020, postgann2020 s <postgann2020@gmail.com> wrote:
On Thursday, May 21, 2020, postgann2020 s <postgann2020@gmail.com> wrote:
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..
***********
Are there any other ways to validate the data, which will help us to improve the performance of the query?
I have no idea what your are trying to get at here. You should try providing SQL that actually runs. Though at first glance it seems quite probable your are doing useless work anyway.
David J.
Hi David,
We are using the below kind of validation throughout the proc in multiple locations and for validation we are using the below statements.
--check Data available or not for structure_id1
IF EXISTS(SELECT 1 FROM schema.table_name WHERE column1=structure_id1) THEN
is_exists1 :=true;
END IF;
IF EXISTS(SELECT 1 FROM schema.table_name WHERE column1=structure_id1) THEN
is_exists1 :=true;
END IF;
We are looking for a better query than "SELECT 1 FROM schema.table_name WHERE column1=structure_id1" this query for data validation.
Please suggest is there any other ways to validate this kind of queries which will improve the overall performance.
Regards,
Postgann.
On Fri, May 22, 2020 at 12:36 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
You should read through the and the contained linked FAQ - note especially the concept and recommendation for “cross-posting”.https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics
On Thursday, May 21, 2020, postgann2020 s <postgann2020@gmail.com> wrote:
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..
***********
Are there any other ways to validate the data, which will help us to improve the performance of the query?I have no idea what your are trying to get at here. You should try providing SQL that actually runs. Though at first glance it seems quite probable your are doing useless work anyway.David J.
Re: Suggestion to improve query performance of data validation in proc.
From
"David G. Johnston"
Date:
On Friday, May 22, 2020, postgann2020 s <postgann2020@gmail.com> wrote:
We are looking for a better query than "SELECT 1 FROM schema.table_name WHERE column1=structure_id1" this query for data validation.
There is no more simple a query that involve records on a single,table.
Please suggest is there any other ways to validate this kind of queries which will improve the overall performance.
Abandon procedural logic and embrace the declarative set oriented nature of SQL.
David J.
On Fri, May 22, 2020 at 2:09 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Friday, May 22, 2020, postgann2020 s <postgann2020@gmail.com> wrote:We are looking for a better query than "SELECT 1 FROM schema.table_name WHERE column1=structure_id1" this query for data validation.
If many rows match potentially, then wrapping the query with select exists(old_query) would allow the execution to bail asap.