Re: Soundness of strategy for detecting locks acquired by DDL statements

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Agis Anastasopoulos <agis(dot)anast(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Soundness of strategy for detecting locks acquired by DDL statements
Date: 2025-05-06 18:31:35
Message-ID: ffa554b9-b945-41b9-8484-3343f172bd01@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/6/25 2:06 AM, Agis Anastasopoulos wrote:
> Hello! I'd like to "preflight" a given schema migration (i.e. one or
> more DDL statements) before applying it to the production database (e.g.
> for use in a CI pipeline). I'm thinking of a strategy and would like to
> know about its soundness.

> Do you think this is a robust way to detect the locks that were
> acquired? Are there any caveats/drawbacks/flaws in this strategy?

Why not just read this?:

https://www.postgresql.org/docs/current/explicit-locking.html

>
> Thanks in advance
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Achilleas Mantzios 2025-05-06 18:58:23 Re: Soundness of strategy for detecting locks acquired by DDL statements
Previous Message Matthew Dennison 2025-05-06 11:09:24 pgdg-redhat-repo-42.0-52PGDG.noarch.rpm missing