| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_waldump stucks with options --follow or -f and --stats or -z |
| Date: | 2021-11-20 06:16:35 |
| Message-ID: | CALj2ACWbgG1bDzXFr6HozpyG8ruhvLt6T1c+PL+UKUW0PGNgEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 20, 2021 at 11:10 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> What you should do is to set such a flag in the signal handler, and
> then check its value in the main loop of pg_waldump, dumping the stats
> if it is detected as turned on because of a signal.
Thanks. Here's the v3 patch, a much simpler one. Please review it.
Regards,
Bharath Rupireddy.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-pg_waldump-emit-stats-while-terminating.patch | application/octet-stream | 4.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-11-20 06:20:24 | Re: Printing backtrace of postgres processes |
| Previous Message | Tom Lane | 2021-11-20 05:55:16 | Re: XLogReadRecord() error in XlogReadTwoPhaseData() |