| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, jian he <jian(dot)universality(at)gmail(dot)com> |
| Subject: | Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION |
| Date: | 2025-05-27 06:00:01 |
| Message-ID: | 488a2abb-4055-4caf-a6ae-3b43fc0615f7@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Yugo,
31.03.2025 14:22, Yugo Nagata wrote:
>> I found that multiple sessions concurrently execute CREATE OR REPLACE FUNCTION
>> for a same function, the error "tuple concurrently updated" is raised. This is
>> an internal error output by elog, also the message is not user-friendly.
> I also found the same error is raised when concurrent ALTER FUNCTION commands are
> executed. I've added a patch to fix this in the similar way.
FWIW, the same error is raised also with concurrent GRANT/REVOKE on a
database:
https://www.postgresql.org/message-id/18dcfb7f-5deb-4487-ae22-a2c16839519a%40gmail.com
Maybe you would also find relevant this thread:
https://www.postgresql.org/message-id/flat/ZiYjn0eVc7pxVY45%40ip-10-97-1-34.eu-west-3.compute.internal
Best regards,
Alexander Lakhin
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-05-27 06:15:44 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | shveta malik | 2025-05-27 05:50:39 | Re: Replication slot is not able to sync up |