Re: Include the dependent extension information in describe command.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Include the dependent extension information in describe command.
Date: 2022-08-14 05:37:46
Message-ID: 566566.1660455466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

vignesh C <vignesh21(at)gmail(dot)com> writes:
> Currently we do not include the dependent extension information for
> index and materialized view in the describe command. I felt it would
> be useful to include this information as part of the describe command
> like:
> \d+ idx_depends
> Index "public.idx_depends"
> Column | Type | Key? | Definition | Storage | Stats target
> --------+---------+------+------------+---------+--------------
> a | integer | yes | a | plain |
> btree, for table "public.tbl_idx_depends"
> Depends:
> "plpgsql"

> Attached a patch for the same. Thoughts?

This seems pretty much useless noise to me. Can you point to
any previous requests for such a feature? If we did do it,
why would we do it in such a narrow fashion (ie, only dependencies
of two specific kinds of objects on one other specific kind of
object)? Why did you do it in this direction rather than
the other one, ie show dependencies when examining the extension?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2022-08-14 05:45:53 Re: Patch proposal: New hooks in the connection path
Previous Message Kazutaka Onishi 2022-08-14 03:59:15 Re: Asynchronous execution support for Custom Scan