| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Executing inet_server_addr/port() in parallel workers |
| Date: | 2021-01-14 03:08:28 |
| Message-ID: | CAD21AoBBq7LjvA7a6J8w9Xm2FOdsbSpf31vMeNThRY36FS+3Pw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 14, 2021 at 6:24 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wrote:
> > Having said that, I'm fine with the idea of just marking these
> > parallel-restricted in HEAD and ignoring the problem in the back
> > branches.
>
> Hearing no complaints, done that way.
Although I thought that backpatching would be helpful for users who
start to use the supported PostgreSQL, I agree not to backpatching
since the likelihood that parallel workers execute these functions is
low.
Thank you for committing the patch!
Regards,
--
Masahiko Sawada
EnterpriseDB: https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-14 03:11:54 | Re: Moving other hex functions to /common |
| Previous Message | Bruce Momjian | 2021-01-14 02:55:34 | Re: Moving other hex functions to /common |