Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
To: Avadhut Narayan Joshi <AJoshi7(at)sensiaglobal(dot)com>
Cc: pgsql-sql(at)lists(dot)postgresql(dot)org
Subject: Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL
Date: 2021-07-29 12:37:17
Message-ID: CAM+6J97VykBs616Wptw6E+Y9O+S_usi9k-9GeNsqr5oXJ=0r_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Thu, Jul 29, 2021, 6:01 PM Avadhut Narayan Joshi <
AJoshi7(at)sensiaglobal(dot)com> wrote:

> Hello Vijaykumar ,
>
>
>
> For SQL Server , when we execute queries using ExecuteNonQuery ,
> InternalRowsAffected is set by default .
>
> Using diagnostics we have to collect and return explicitly for further
> work flow .
>
>
>
> So is there any out-of-box equivalent in PostgreSQL
>

OK, honestly I do not know much about sql server.
You can run explain, on the query to get an estimated rows that would be
touched at each node layer.
explain analyze, would give estimated and real number of rows touched at
each node layer.
There are stats updated in pg_stat_all_tables catalog for the relevant
table for ins, upd, del etc but that is cumulative at the db layer, not
sure if that can be useful at per query layer.
I think in that case, someone else would chime in with more exp.

>
>
>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Steve Midgley 2021-07-29 19:43:02 Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL
Previous Message Avadhut Narayan Joshi 2021-07-29 12:31:20 RE: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL