Re: Adjust pg_stat_get_lock() prorows to match lock types

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: li(dot)evan(dot)chao(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Adjust pg_stat_get_lock() prorows to match lock types
Date: 2026-06-08 18:46:12
Message-ID: 581812.1780944372@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> writes:
> This discussion also made me wonder whether the documentation could be
> a bit more explicit that prorows is intended as a planner estimate
> rather than an exact row count.

>> Estimated number of result rows (zero if not proretset)

+1. For the most part, I'd expect that to be obvious from the
fact that it's a constant ... but maybe being explicit would help.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marcos Pegoraro 2026-06-08 19:11:05 Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
Previous Message Tom Lane 2026-06-08 18:43:22 Re: Fix DROP PROPERTY GRAPH "unsupported object class" error