| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgrade should truncate/remove its logs before running |
| Date: | 2021-12-16 11:23:08 |
| Message-ID: | E66B93B0-8579-48BC-9CA4-4C6E3A97408D@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 16 Dec 2021, at 12:11, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> Could we make it write just one log file? Is having multiple log files better?
Having individual <checkname>.txt files from checks with additional information
on how to handle the error are quite convenient when writing wrappers around
pg_upgrade (speaking from experience of having written multiple pg_upgraade
frontends). Parsing a single logfile is more work, and will break existing
scripts.
I'm in favor of a predictable by default logpath, with a parameter to override,
as mentioned upthread.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-12-16 11:23:11 | Re: Transparent column encryption |
| Previous Message | Peter Eisentraut | 2021-12-16 11:11:25 | Re: pg_upgrade should truncate/remove its logs before running |