Re: Temp schema drop leaves an inconsistent state behind - Mailing list pgsql-hackers

From Manu
Subject Re: Temp schema drop leaves an inconsistent state behind
Date
Msg-id 179030634615.636939.4639430401701705347@gmail.com
Whole thread
In response to Re: Temp schema drop leaves an inconsistent state behind  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Hi Michael,

Michael Paquier <michael@paquier.xyz> wrote:
> My point being: we did not care back then for the reasons given back
> then related to superusers.  Why should we care now?

Fair enough.  It was settled back then, and I'll leave it there.

> This comment does not apply only to this thread, more to the recent
> activities of this email address: note that most of your reviews,
> being clearly AI-generated, are rather noisy (not all, but a large
> majority), and sometimes miss the point while providing a sloppy
> amount of confusing contents.

Thanks for saying it plainly.  Yes, I use AI tooling: it builds the
patched trees, runs the tests and collects the numbers, and every
result I post comes from those runs.  Deciding what is worth posting
is my part, and here I got it wrong: I went into how to fix this
before weighing whether it should be fixed, which had already been
answered in 2019.  I'll take myself off the commitfest entry, and
keep reviews short and to what a thread actually needs.

Regards,
Manu



pgsql-hackers by date:

Previous
From: Osama Abdul Qader
Date:
Subject: Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
Next
From: shihao zhong
Date:
Subject: Re: Add a permission check to pg_stat_get_backend_subxact()