| From: | Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | FIX: BUG #19687: ALTER SEQUENCE missing lock |
| Date: | 2026-09-15 06:49:31 |
| Message-ID: | CAE8JnxNPC6MjO4xN2k_r+jxG38PLmKa7CtWRMnJxvL==ZoFdWw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Trying to do something different today.
Hunting bugs.
Addressing an issue in `ALTER SEQUENCE` commands [1], by adding
a missing lock when calling RelationSetNewRelfilenumber and being
more accurate about the type of lock required in that function's
doc-comment.
The change is sound, even if it is not the complete fix yet.
1.
https://www.postgresql.org/message-id/19687-dd094472b0c48afb%40postgresql.org
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-FIX-missing-lock-in-AlterSequence.patch | application/octet-stream | 1.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2026-09-15 06:50:49 | Re: bug, ALTER TABLE call ATPostAlterTypeCleanup twice for the same relation |
| Previous Message | Ashutosh Bapat | 2026-09-15 06:42:55 | property graph and pg_dump |