On 05.09.2024 23:32, Euler Taveira wrote:
On Thu, Sep 5, 2024, at 1:05 PM, Ilia Evdokimov wrote:
It's quite common that poor query performance can be attributed to
inaccurate row estimations by the planner. To make it easier to
detect these discrepancies, rather than scrutinizing the estimat
On Thu, Sep 5, 2024, at 5:32 PM, Euler Taveira wrote:
> $ cat /tmp/pcc.pl
> #!/usr/bin/perl -n
> print "\033[1m\033[35m$1\033[36m$2\033[32m$3\033[33m$4\033[m" while
> /([|+-]+)|([0-9]+)|([a-zA-Z_]+)|([^\w])/g;
>
> and then you can start psql as:
>
> $ PAGER="/c/mypager.pl" psql
I meant:
$ PAGE
On Thu, Sep 5, 2024, at 1:05 PM, Ilia Evdokimov wrote:
> It's quite common that poor query performance can be attributed to inaccurate
> row estimations by the planner. To make it easier to detect these
> discrepancies, rather than scrutinizing the estimates manually, it would be
> helpful to ou
Hi hackers,
It's quite common that poor query performance can be attributed to
inaccurate row estimations by the planner. To make it easier to detect
these discrepancies, rather than scrutinizing the estimates manually, it
would be helpful to output a dedicated |NOTICE| message.
In the curre
