That sounds like the ability to do something like EXPLAIN CREATE INDEX ... is that correct?
Yes, and I suppose this would be quite some work to do. Though I see how interesting it would be, and a nice project to hack on.
> So do we really want to do what's proposed here? I'm +-0 about the > VERBOSE option attached to more commands, as it is a bit harder for > clients to catch the information wanted.
It sounds to me a lot easier to know about a VERBOSE option that gives you more information, than using a DEBUG level to get the same information. DEBUG level messages aren't explained in the CREATE INDEX manpage, whereas a VERBOSE option would be.
So here comes my question: > how do we want to consume this information at the end from the > perspective of the client?
For interactive usage in psql or pgadmin, it's trivial to capture this information.
+1
The information can also be written to the server log with log_min_messages=INFO
A bit more work is required to redirect messages to an out file from psql, as you need to ensure that stderr is redirected to a file. It's also a bit more work to capture this information from something like a JDBC application.
IMO the interactive use-case is where this is the most useful as you can start a CREATE INDEX (VERBOSE) and ensure that it's going to launch all the parallel workers that it planned before letting it it continue; or control-c and figure out why not all planned workers launched.
