| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: remove "msg" parameter from convert_tuples_by_name |
| Date: | 2019-09-04 01:38:07 |
| Message-ID: | CA+HiwqGOUzVLimAMOdebvYJJSDYJvPpPjnhwP56qXeWV2-zN3Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 4, 2019 at 3:52 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> On 2019-Aug-07, Amit Langote wrote:
>
> > If we're reducing the message string to occur only once in the source
> > code, can we maybe write it to be more informative? I wonder if users
> > aren't normally supposed to see this message?
>
> Grepping for the messages given to convert_tuples_by_position yields
> quite a few matches in regression test output, but none for the one in
> convert_tuples_by_name. This makes me think that it isn't user-visible,
> unless things go very wrong.
>
> Pushed the patch, thanks.
Thanks. I thought you'd change the ereport to elog while at it.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-09-04 01:38:58 | Re: Proposal: roll pg_stat_statements into core |
| Previous Message | Alexey Zagarin | 2019-09-04 01:21:27 | Re: row filtering for logical replication |