Re:unexpected plan with id = any('{}') condition

Sergei Kornilov <sk@zsrv.org>

From: Sergei Kornilov <sk@zsrv.org>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: PostgreSQL mailing lists <pgsql-hackers@lists.postgresql.org>

Date: 2021-11-11T18:15:54Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: Add referential actions to CREATE/ALTER TABLE synopsis
- db9f287711ac 15.0 cited

Hello

Thank you for the explanation!

> unreadable HTML mess

ouch, sorry. "Nobody uses plain text mail, we dropped this thing in the interface” said yandex team. (I know that some members of the Yandex team read mailing lists, could you ping your colleagues?)

> but I'm not convinced we want to expend
> extra cycles looking for such cases.

Agree. This is an application bug and needs to be fixed there. There is no point in slowing down all queries for the sake of improving an inherently erroneous query condition.

regards, Sergei