| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Inconsistent error message wording for REINDEX CONCURRENTLY |
| Date: | 2019-05-29 21:34:20 |
| Message-ID: | CA+Tgmobb9=-PhJGbuxdkRr7xtyqVWM+vGa3hxBz3WxKpNV0OdA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 27, 2019 at 4:02 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Mon, May 27, 2019 at 12:20:58AM -0400, Alvaro Herrera wrote:
> > I wonder if we really want to abolish all distinction between "cannot do
> > X" and "Y is not supported". I take the former to mean that the
> > operation is impossible to do for some reason, while the latter means we
> > just haven't implemented it yet and it seems likely to get implemented
> > in a reasonable timeframe. See some excellent commentary about about
> > the "can not" wording at
> > https://postgr.es/m/CA+TgmoYS8jKhETyhGYTYMcbvGPwYY=qA6yYp9B47MX7MweE25w@mail.gmail.com
>
> Incorrect URL?
That's one of my messages that never made it through to the list.
Try http://postgr.es/m/CA+TgmoZ0HZuLGVLkF_LRTNYDijic4nqd-EpCDf_NgtMksfNL1g@mail.gmail.com
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-05-29 21:51:37 | Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3 |
| Previous Message | Robert Haas | 2019-05-29 21:32:45 | Re: message style |