From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Fixed malformed error message on malformed SCRAM message. |
Date: | 2017-05-29 21:40:21 |
Message-ID: | 20170529214021.kaw5qjzsbofaa6re@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier wrote:
> On Mon, May 29, 2017 at 2:06 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > These messages look all wrong to me.
>
> So your complain would be to do the following for each error message
> that uses parenthesis to include details? Like that I suppose:
> --- a/src/backend/libpq/auth-scram.c
> +++ b/src/backend/libpq/auth-scram.c
> @@ -283,11 +283,13 @@ pg_be_scram_exchange(void *opaq, char *input,
> int inputlen,
> if (inputlen == 0)
> ereport(ERROR,
> (errcode(ERRCODE_PROTOCOL_VIOLATION),
> - (errmsg("malformed SCRAM message (empty message)"))));
> + errmsg("malformed SCRAM message"),
> + errdetail("Empty message.")));
Yeah, but along the lines of errdetail("The message is empty.")
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Gustavo Campos | 2017-05-29 22:08:52 | PGDG Repository for RHEL6 is bronen, populated with RHEL7 packages |
Previous Message | Michael Paquier | 2017-05-29 21:31:02 | Re: [PATCH] Fixed malformed error message on malformed SCRAM message. |
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2017-05-29 21:49:33 | Re: logical replication busy-waiting on a lock |
Previous Message | Michael Paquier | 2017-05-29 21:31:02 | Re: [PATCH] Fixed malformed error message on malformed SCRAM message. |