Re: Errands around AllocateDir()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>,
PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-12-04T19:00:13Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Dec 4, 2017 at 12:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> The only part of this that seems likely to be controversial is the >> decision to get rid of special-case error messages, eg replace >> "could not open tablespace directory \"%s\": %m" >> with the more generic >> "could not open directory \"%s\": %m" >> As I said in the previous thread, I don't see anything much wrong >> with that; but if anyone doesn't like it, speak now. > I find that change an improvement, but not something to back-patch. Yeah, agreed. The only thing I'm concerned about back-patching is the places where a wrong errno might be reported. regards, tom lane
Commits
-
Clean up assorted messiness around AllocateDir() usage.
- 2069e6faa0f7 11.0 landed
- eccb786f471b 9.5.11 landed
- 5eefe7452ed0 9.3.21 landed
- 543d8c2f5d4c 9.6.7 landed
- 2a11b188e8ab 10.2 landed
- 225501cf754f 9.4.16 landed