| From: | zengman <zengman(at)halodbtech(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Junwang Zhao <zhjwpku(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
| Subject: | Re: (SQL/PGQ) cache lookup failed for label |
| Date: | 2026-06-05 14:37:43 |
| Message-ID: | tencent_2F6622B5506146817B1B7DCD@qq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> b won't be dropped since vl3 references it. But c should get dropped.
> It will be interesting to see what happens if someone tries to add a
> label with property c afterwards with a different data type - it will
> fail, I guess. It's worth fixing for that case if nothing else.
>
> We have gathered 3 issues in this thread, which depend upon each other
> either because of code or the test queries. Can you please start a new
> thread to discuss this and provide a patch fixing it?
Hi Ashutosh,
You're right, I pasted the wrong test case. I've started a new thread
for this issue with the correct repro and patch. Please see:
https://www.postgresql.org/message-id/tencent_76F6ACA2364EAA1E5DBD7A47%40qq.com
--
regards,
Man Zeng
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-06-05 14:43:16 | Re: Prevent remote libpq notices from being sent to clients |
| Previous Message | zengman | 2026-06-05 14:29:12 | (SQL/PGQ) Clean up orphaned properties when dropping a label |