| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Ayub Khan <ayub(dot)hp(at)gmail(dot)com> |
| Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: waiting for client write |
| Date: | 2021-06-11 18:03:03 |
| Message-ID: | CAEudQArD0ndY=SOOQ7MhWgQRdZhbJVkg+T5WW0jf=bhT_wkamQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Em sex., 11 de jun. de 2021 às 14:59, Ayub Khan <ayub(dot)hp(at)gmail(dot)com>
escreveu:
> Ranier,
>
> I tried to VACCUM ANALYZE the tables involved multiple times and also
> tried the statistics approach as well
>
Ayub you can try by the network side:
" We found out that this was caused by the database server's MTU setting.
MTU was set to 9000 by default and resulted in packet loss. Changing it to
1500 resolved the issue."
regards,
Ranier Vilela
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayub Khan | 2021-06-11 18:19:19 | Re: waiting for client write |
| Previous Message | Ayub Khan | 2021-06-11 17:59:07 | Re: waiting for client write |