From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Errands around AllocateDir() |
Date: | 2017-12-04 17:42:24 |
Message-ID: | CA+TgmoYqELNAX_1b2=-7YLhXkTSEMZ1u6mz=BxuryZrx_Krpgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 4, 2017 at 12:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> I had a close look at all the callers of AllocateDir() and noticed a
>> couple of unwelcome things (Tom noticed some of those in the thread
>> mentioned above, I found others):
>
> 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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pantelis Theodosiou | 2017-12-04 17:44:31 | Re: [HACKERS] Secondary index access optimizations |
Previous Message | Andrey Borodin | 2017-12-04 17:40:18 | Re: [HACKERS] WIP: Covering + unique indexes. |