Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?
От | Tom Lane |
---|---|
Тема | Re: improve DEBUG1 logging of parallel workers for CREATE INDEX? |
Дата | |
Msg-id | 1692530.1736369905@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: improve DEBUG1 logging of parallel workers for CREATE INDEX? (Sami Imseih <samimseih@gmail.com>) |
Ответы |
Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?
|
Список | pgsql-hackers |
Sami Imseih <samimseih@gmail.com> writes: > I am curious what are the thoughts on introducing a > CREATE INDEX VERBOSE which can provide this info? > similar to users scripting VACUUM VERBOSE to log > more details about the vacuum operation including parallel > usage. What I can recall being discussed in the past is to extend EXPLAIN and/or EXPLAIN ANALYZE to cover utility statements that have nontrivial execution complexity --- for example, ALTER TABLE has a lot of machinery underneath, and people often wish to know things like whether a particular ALTER will cause a table rewrite or not. Of course, a patch for that would be a few orders of magnitude larger than what you've got here :-(. But if you're looking for a framework for reporting these sorts of details, I'd much rather go in that direction than follow the model of VACUUM VERBOSE. VACUUM VERBOSE is a kluge with little to recommend it other than having been easy to implement. regards, tom lane
В списке pgsql-hackers по дате отправления: