From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrade generated files in subdir follow-up |
Date: | 2022-08-31 13:59:27 |
Message-ID: | 4061927.1661954367@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> Commit 38bfae36526 moved the .txt files pg_upgrade generates to a separate
> subdir, but there are a few left which are written to cwd. The thread
> resulting in that patch doesn't discuss these files specifically so it seems
> they are just an oversight. Unless I'm missing something.
> Should something the attached be applied to ensure all generated files are
> placed in the subdirectory?
It certainly looks inconsistent ATM. I wondered if maybe the plan was to
put routine output into the log directory but problem-reporting files
into cwd --- but that isn't what's happening now.
As long as we report the path to where the file is, I don't see a reason
not to put problem-reporting files in the subdir too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-08-31 14:01:28 | pg15b3: recovery fails with wal prefetch enabled |
Previous Message | Imseih (AWS), Sami | 2022-08-31 13:15:02 | Re: [BUG] Panic due to incorrect missingContrecPtr after promotion |