Re: PostgreSQL log query's result size
| От | Hellmuth Vargas |
|---|---|
| Тема | Re: PostgreSQL log query's result size |
| Дата | |
| Msg-id | CAN3Qy4oH3FSp5aAOrmLRxCrqJ=vXJ5t66pfnvw3aWj32DF6Q5g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL log query's result size (Justin Pryzby <pryzby@telsasoft.com>) |
| Ответы |
Re: PostgreSQL log query's result size
|
| Список | pgsql-hackers |
?? Well, the truth does not show the data that I request, what I request is that by configuring some parameter, the size of the obtained records can be obtained from the execution of a query something similar to the log_min_duration_statement parameter
Now I think it is pertinent to write here because, according to I have carefully reviewed the documentation, this functionality does not exist
Now I think it is pertinent to write here because, according to I have carefully reviewed the documentation, this functionality does not exist
El mar, 6 de abr. de 2021 a la(s) 14:15, Justin Pryzby (pryzby@telsasoft.com) escribió:
On Tue, Apr 06, 2021 at 02:03:03PM -0500, Hellmuth Vargas wrote:
> Could you tell me if it is possible that as well as the configuration that
> the log presents the duration of the delayed queries, it can also present
> the size of the result data? especially those who want to return a lot of
> information
I think you can get what you want by with auto_explain.
https://www.postgresql.org/docs/current/auto-explain.html
You can set:
auto_explain.log_analyze
And then the "width" and "rows" are logged:
Result (cost=0.00..0.01 rows=1 width=4) (actual time=0.002..0.004 rows=1 loops=1)
PS, you should first ask on the pgsql-general list, rather than this
development list.
--
Justin
--
Cordialmente,
Ing. Hellmuth I. Vargas S.
Esp. Telemática y Negocios por Internet
Ing. Hellmuth I. Vargas S.
Esp. Telemática y Negocios por Internet
Oracle Database 10g Administrator Certified Associate
EnterpriseDB Certified PostgreSQL 9.3 Associate
В списке pgsql-hackers по дате отправления: