| From: | Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | more detailed description of tup_returned and tup_fetched |
| Date: | 2021-05-14 08:00:45 |
| Message-ID: | 9eeeccdb-5dd7-90f9-2807-a4b5d2b76ca3@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hi,
I worried the difference between "tup_returned" and "tup_fetched" in
pg_stat_database. I assumed that "tup_returned" means the number of tuples
that returned to clients. Of course, this is wrong.
So, why don't you describe in more detail? If my understanding is right, they
correspond to "seq_tup_read" and "idx_tup_fetch" in pg_stat_all_tables.
Regards,
--
Masahiro Ikeda
NTT DATA CORPORATION
| Attachment | Content-Type | Size |
|---|---|---|
| add-more-detailed-description-of-tup_returned-and-tup_fetched.patch | text/x-patch | 936 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-05-17 06:32:38 | Re: more detailed description of tup_returned and tup_fetched |
| Previous Message | David G. Johnston | 2021-05-13 21:12:42 | Re: Where is the syntax "<-08>+08" documented—comes from "select current_setting('timezone')" |