| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, florisvannee(at)optiver(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: error "can only drop stats once" brings down database |
| Date: | 2024-06-07 09:32:13 |
| Message-ID: | ZmLTneAb+EaZMS9A@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Thu, Jun 06, 2024 at 08:12:58PM -0700, Andres Freund wrote:
> On 2024-06-07 11:46:04 +0900, Michael Paquier wrote:
> > On Fri, Jun 07, 2024 at 10:15:40AM +0900, Kyotaro Horiguchi wrote:
> > > To me, this is something that is not expected to happen, but if it
> > > does, we would want detailed information. In that sense, it might be
> > > better not to hide it in the DETAILS field.
> >
> > Same arguments here. A simple elog() makes easier to get to this
> > data.
>
> +1
That was a nit, so fine by me to move on with a simple elog().
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Koval | 2024-06-07 09:45:26 | Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature? |
| Previous Message | Etsuro Fujita | 2024-06-07 09:10:44 | Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption |