| From: | keisuke kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Alexey Bashtanov <bashtanov(at)imap(dot)cc>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: control max length of parameter values logged |
| Date: | 2020-03-18 05:04:06 |
| Message-ID: | CANDwggKD_0H0y+4q9KxB7umio=qs9ka1HAY4g8XaDfZPYm=cvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
BIND parameter truncation is good to me.
Logs could be very hard to read due to
the very long parameters recorded.
Now, parameter is extracuted from left.
e.g. "AAAA-BBBB-CCCC-DDDD-EEEE" to "AAAA-BBBB-CCCC..."
Is not necessary from right?
e.g. "AAAA-BBBB-CCCC-DDDD-EEEE" to "...CCCC-DDDD-EEEE"
It is sometimes nice to be able to check
the last of strings. For example, if there
are difference only in the last of strings
of many parameters.
Best Regards,
Keisuke Kuroda
| From | Date | Subject | |
|---|---|---|---|
| Next Message | p.b uday | 2020-03-18 05:11:31 | GSoC applicant proposal, Uday PB |
| Previous Message | Andy Fan | 2020-03-18 04:57:57 | Re: [PATCH] Erase the distinctClause if the result is unique by definition |