Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Philip Alger <paalger0(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement
Date: 2025-10-18 17:01:05
Message-ID: CAB-JLwb=7chi75J9Nfsi+aiHTbUTa7b02m1mezMZMM=AoMaytg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em sáb., 18 de out. de 2025 às 12:19, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
escreveu:

> Other than that, the patch LGTM. If the other reviewers have no
> objections, I'll mark it as ready for committer.
>

Before committing, thinking of all these features, triggers, constraints,
tables, etc, to be all of them really useful, wouldn't it be better to have
an option to drop them first or create if not exists when available ?

pg_get_trigger_ddl(oid, pretty, drop_first) ?

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shinya Kato 2025-10-18 17:04:18 Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls
Previous Message Arseniy Mukhin 2025-10-18 16:41:46 Re: Optimize LISTEN/NOTIFY