Re: Query Plan Columns
От | David E. Wheeler |
---|---|
Тема | Re: Query Plan Columns |
Дата | |
Msg-id | 190D4156-3191-4209-9939-9F1D2C8D2B41@kineticode.com обсуждение исходный текст |
Ответ на | Re: Query Plan Columns ("David E. Wheeler" <david@kineticode.com>) |
Ответы |
Re: Query Plan Columns
|
Список | pgsql-hackers |
On Nov 5, 2010, at 1:42 PM, David E. Wheeler wrote: >> http://git.postgresql.org/gitweb?p=postgresql.git;a=blob;f=src/backend/commands/explain.c;h=f494ec98e510c23120e072bd5ee8821ea12738a4;hb=HEAD#l617 > > Ah, great, thanks. So based on this, I've come up with: "Node Type" TEXT, "Strategy" TEXT, "Operation" TEXT, "Startup Cost" FLOAT, "Total Cost" FLOAT, "Plan Rows" FLOAT, "Plan Width" INTEGER, "Actual StartupTime" FLOAT, "Actual Total Time" FLOAT, "Actual Rows" FLOAT, "Actual Loops" FLOAT, "Parent Relationship" TEXT, "Sort Key" TEXT[], "Sort Method" TEXT[], "Sort Space Used" BIGINT, "Sort Space Type" TEXT, "Join Type" TEXT, "Join Filter" TEXT, "HashCond" TEXT, "Relation Name" NAME, "Alias" NAME, "Scan Direction" TEXT, "Index Name" TEXT, "Index Cond" TEXT, "Recheck Cond" TEXT, "TID Cond" TEXT, "Merge Cond" TEXT, "Subplan Name" TEXT, "Function Name" TEXT, "Function Call" TEXT, "Filter" TEXT, "One-Time Filter" TEXT, "Command" TEXT, "SharedHit Blocks" BIGINT, "Shared Read Blocks" BIGINT, "Shared Written Blocks" BIGINT, "Local Hit Blocks" BIGINT, "Local Read Blocks" BIGINT, "Local Written Blocks" BIGINT, "Temp Read Blocks" BIGINT, "TempWritten Blocks" BIGINT, "Output" TEXT[], "Hash Buckets" BIGINT, "Hash Batches" BIGINT, "Original Hash Batches" BIGINT, "Peak Memory Usage" BIGINT, "Schema" TEXT, "CTE Name" TEXT Does that seem reasonable? Am I missing anything obvious? Thanks, David
В списке pgsql-hackers по дате отправления: