Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL - Mailing list pgsql-sql

From Steve Midgley
Subject Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL
Date
Msg-id CAJexoS+Lj1HCRic=adnyswqJ5FCky4nXUtPBXiJODHwZdvcReA@mail.gmail.com
Whole thread Raw
In response to Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL  (Vijaykumar Jain <vijaykumarjain.github@gmail.com>)
List pgsql-sql


On Thu, Jul 29, 2021 at 5:37 AM Vijaykumar Jain <vijaykumarjain.github@gmail.com> wrote:


On Thu, Jul 29, 2021, 6:01 PM Avadhut Narayan Joshi <AJoshi7@sensiaglobal.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.


My recollection (hazy) is that for my ORM wrapper of choice (ActiveRecord for Ruby), the AR Pg driver returns the number of rows affected and I just relied on that. (cf https://stackoverflow.com/questions/27552542/affected-rows-for-activerecordbase-connection-execute). 

I hope this input is helpful,
Steve

pgsql-sql by date:

Previous
From: Vijaykumar Jain
Date:
Subject: Re: Equivalent of InternalRowsAffected in NonExecuteQuery for PostgreSQL
Next
From: Rockdale Green
Date:
Subject: How to generate the order if you know the next item for each item?