| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: A new message seems missing a punctuation |
| Date: | 2024-02-20 11:20:27 |
| Message-ID: | CA+TgmoZXDXe7Ey3_7G+s_g+KKq4B2KRtEepXHK+fvaJYA1iFTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 20, 2024 at 4:42 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > So why do we log a message about this?
>
> This was added after the main commit of this functionality to find
> some BF failures (where we were expecting the slot to sync but due to
> one of these conditions not being met the slot was not synced) and we
> can probably change it to DEBUG1 as well. I think we would need this
> information w.r.t this functionality to gather more information in
> case expected slots are not being synced and it may be helpful for
> users to also know why the slots are not synced, if that happens.
Ah, OK. Do you think we need any kind of system view to provide more
insight here or is a log message sufficient?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-02-20 11:27:02 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |
| Previous Message | Peter Eisentraut | 2024-02-20 11:18:57 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |