Re: [PATCH] Add pretty formatting to pg_get_triggerdef

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Alger <paalger0(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add pretty formatting to pg_get_triggerdef
Date: 2025-11-05 19:29:29
Message-ID: 876011.1762370969@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Alger <paalger0(at)gmail(dot)com> writes:
> I am attaching v3.

This patch will cause psql's \d to fail hard against any pre-v19
server. That's not acceptable. Note the comment at the top of
describe.c:

* Support for the various \d ("describe") commands. Note that the current
* expectation is that all functions in this file will succeed when working
* with servers of versions 9.2 and up. It's okay to omit irrelevant
* information for an old server, but not to fail outright. (But failing
* against a pre-9.2 server is allowed.)

You could get around that with a conditional on the server version,
as is done elsewhere in describe.c. But I kind of wonder why we
need this new function at all. Isn't "pg_get_triggerdef(oid, false)"
close enough?

An alternative suggestion is to keep "pg_get_triggerdef(oid, true)"
doing exactly what it does today and have the newly-introduced
function be the one that has new behavior. This might be a smarter
plan anyway to avoid side-swiping other clients that are expecting
the current behavior.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-11-05 19:42:12 Re: inconsistent tableoid handling in COPY WHERE clause
Previous Message Matheus Alcantara 2025-11-05 19:02:52 Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue