Re: try_relation_open and relation_open behave different.
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Xing GUO <higuoxing@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org
Date: 2021-10-18T13:44:24Z
Lists: pgsql-hackers
On 2021-Oct-18, Xing GUO wrote: > However, I can open an "uncommitted" relation using relation_open() and > cannot open it using try_relation_open(). > Since Postgres doesn't write the "uncommitted" relation descriptor to > SysCache and try_relation_open() checks if the > relation exists in SysCache while relation_open() doesn't check it. Hmm, is it sufficient to do CommandCounterIncrement() after your "uncommitted" relation change and the place where you do try_relation_open()? -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ "Linux transformó mi computadora, de una `máquina para hacer cosas', en un aparato realmente entretenido, sobre el cual cada día aprendo algo nuevo" (Jaime Salinas)
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Detect POLLHUP/POLLRDHUP while running queries.
- c30f54ad732c 14.0 cited