| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug on log generation ? |
| Date: | 2022-08-08 18:34:27 |
| Message-ID: | CAB-JLwbmBcGGjxJR7Q+5WfP7kH9DzjSR_cBDHrv71NT9HJ_AbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> OK, we really need a repeatable test if possible. Perhaps a pgbench run
> with lots of concurrent runs of a some very long query would do the trick.
>
OK, I can do it but ... strangely that error usually occurs at random
times, sometimes at 08:00, sometimes at 19:00, and it's busier between
10:00 and 16:00. If I cron some of those queries to run every second is
enough ? What exactly do you expect to see on log files ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2022-08-08 18:35:25 | Re: 2022-08-11 release announcement draft |
| Previous Message | Antonin Houska | 2022-08-08 18:27:27 | Re: Temporary file access API |