Re: Add psql command to list constraints
От | Tatsuro Yamada |
---|---|
Тема | Re: Add psql command to list constraints |
Дата | |
Msg-id | 0fd675eb-026f-5abb-5cba-d5eb66c7fa12@nttcom.co.jp обсуждение исходный текст |
Ответ на | Re: Add psql command to list constraints (Greg Stark <stark@mit.edu>) |
Ответы |
Re: Add psql command to list constraints
|
Список | pgsql-hackers |
Hi All, > In the interests of trying to clean up the CF and keep things moving > I'll mark the patch rejected. Thank you for managing the commitfest and the comments from many of hackers. I apologize for not being able to email you more often due to my busy day job. First of all, I understand to a certain extent your opinion that we can use \d and look at the constraints on a table-by-table basis as a way to check the constraints. However, suppose We want to reverse lookup a table from a constraint. In that case, there are two ways: (1) use "\d" to lookup all tables, (2) execute a select statement against pg_constraint. I think the proposed function is more valuable than these. From another perspective, when looking at the comprehensiveness of metacommands in psql, it seems that only functions that focus on constraints do not exist. Therefore, It would be better to add it in terms of comprehensiveness. I think there is room for other discussions about this patch. Still, at least there are people (including myself) who think it is useful. I don't think there is anything wrong with this patch that would complicate the code or cause performance degradation, so I would like to continue developing it for those who want to use it. However, I understand that it will not be ready in time for PG15, so I would like to move forward with PG16. Therefore, the status of the patch would be better by changing "Waiting for Author" rather than "Rejected". P.S. I'll send a new patch addressing Dag's comments in the next email. Thanks, Tatsuro Yamada
В списке pgsql-hackers по дате отправления: