| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tatsuro Yamada <yamada(dot)tatsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, bruce(at)momjian(dot)us |
| Subject: | Re: Postgres 11 release notes |
| Date: | 2018-07-09 05:28:15 |
| Message-ID: | 20180709052815.lh55klasauvhb4ii@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On 2018-07-09 14:18:14 +0900, Tatsuro Yamada wrote:
> Hi Bruce,
>
> > I expect a torrent of feedback.;-)
>
> Could you add this fix to the release note because this change affects
> an extension developer using the hook function.
> It would be better to know the change by reading the release note, not compilation error.
>
> <!--
> 2017-01-11 [4d41b2e09] Add QueryEnvironment to ExplainOneQuery_hook's parameter list.
> -->
> <para>
> Add QueryEnvironment to ExplainOneQuery_hook's parameter list
> (Tatsuro Yamada, Thomas Munro)
> </para>
>
> Discussion: https://postgr.es/m/890e8dd9-c1c7-a422-6892-874f5eaee048@lab.ntt.co.jp
>
> I guess "E.1.3.11. Source Code" or "E.1.3.12. Additional Modules" sections are
> suitable for putting the message in the release note.
We adapt plenty of functions signatures without listing them
individually in the release notes. I don't think randomly selecting one
relatively uncommonly used hook is a good way to attack that.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2018-07-09 05:39:34 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Previous Message | Michael Paquier | 2018-07-09 05:18:51 | Re: Non-reserved replication slots and slot advancing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-07-09 14:36:30 | Re: Postgres 11 release notes |
| Previous Message | Tatsuro Yamada | 2018-07-09 05:18:14 | Re: Postgres 11 release notes |