From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | x4mmm(at)yandex-team(dot)ru, andrew(at)tao11(dot)riddles(dot)org(dot)uk, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Dimension limit in contrib/cube (dump/restore hazard?) |
Date: | 2018-08-30 14:09:33 |
Message-ID: | CAPpHfdtUUhuQPCqi-NHt7Z8-GM+2uXRQvNZxWqeuzqkYz=31VA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 30, 2018 at 4:59 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> > I'm going to check this patchset on Windows and commit if no objections.
>
> These error messages do not conform to our message style guidelines:
> you've copied an errdetail message as primary error message, but the
> rules are different for that (no complete sentences, no initial cap,
> no period).
>
> Using ERRCODE_ARRAY_ELEMENT_ERROR seems pretty random as well --- so far
> as I can see, that's generally used for cases like "this array has the
> wrong type of data elements". Perhaps ERRCODE_PROGRAM_LIMIT_EXCEEDED
> would be the best choice.
Thank you for catching this! I'll be more careful about error messages.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment | Content-Type | Size |
---|---|---|
0001-cube-split-scientific-notation-test-v2.patch | application/x-patch | 55.1 KB |
0002-cube-enforce-dimension-checks-v2.patch | application/octet-stream | 10.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2018-08-30 14:22:37 | Re: Proposal for disk quota feature |
Previous Message | Tom Lane | 2018-08-30 14:04:55 | Re: Startup cost of sequential scan |