| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | proposal - log_full_scan |
| Date: | 2021-04-17 14:36:52 |
| Message-ID: | CAFj8pRBeP78aLc5Psd2cpbso8mY4bmTvHfayJ+yqrpoOF0v0Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
today I worked on postgres's server used for critical service. Because the
application is very specific, we had to do final tuning on production
server. I fix lot of queries, but I am not able to detect fast queries that
does full scan of middle size tables - to 1M rows. Surely I wouldn't log
all queries. Now, there are these queries with freq 10 per sec.
Can be nice to have a possibility to set a log of queries that do full
scan and read more tuples than is specified limit or that does full scan of
specified tables.
What do you think about the proposed feature?
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-04-17 15:09:31 | Re: proposal - log_full_scan |
| Previous Message | Andrew Dunstan | 2021-04-17 13:55:47 | Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows |