Re: query_id, pg_stat_activity, extended query protocol - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: query_id, pg_stat_activity, extended query protocol
Date
Msg-id 04B31A72-7BB4-4BB2-AA3E-9B4F2B611BBE@gmail.com
Whole thread Raw
In response to Re: query_id, pg_stat_activity, extended query protocol  (Sami Imseih <samimseih@gmail.com>)
List pgsql-hackers
> I am not sure. The GUCs pretty much enforce this behavior and I doubt
> that these are going to break moving on. Of course they would, but we
> are usually careful enough about that as long as it is possible to
> grep for them. For example see the BRIN case in pageinspect.

Yes, I see pageinspect does the same thing for the BRIN case.
That is probably OK for this case also.

> The usual method for output that we use to confirm parallelism would
> be EXPLAIN. Perhaps a potential target for CREATE INDEX now that it
> supports more modes? I don't know if that's worth it, just throwing
> one idea in the bucket of ideas.

Not sure about EXPLAIN for CREATE INDEX, since it's not a plannable
statement.

Maybe a CREATE INDEX VERBOSE, just Like  ANALYZE VERBOSE, 
VACUUM VERBOSE, etc. This will show the step that an index 
build is on (CONCURRENTLY has many steps), and can also show 
if parallel workers are launched for the index build.

--

Sami 






pgsql-hackers by date:

Previous
From: Yugo NAGATA
Date:
Subject: Re: Add has_large_object_privilege function
Next
From: Amit Langote
Date:
Subject: Re: ALTER TABLE ONLY .. DROP CONSTRAINT on partitioned tables