From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is this a feature? |
Date: | 2007-06-11 18:35:48 |
Message-ID: | 466D9604.9060002@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> Take the following:
>
> INFO: analyzing "pg_catalog.pg_authid"
> INFO: "pg_authid": scanned 1 of 1 pages, containing 5 live rows and 0
> dead rows; 5 rows in sample, 5 estimated total rows
>
> The above is completely redundant. Why not just say:
>
> INFO: "pg_authid": scanned 1 of 1 pages, containing 5 live rows and 0
> dead rows; 5 rows in sample, 5 estimated total rows
>
> If the first line is meant to be an indicator, then make the above line
> do this:
>
> INFO: analyzing "pg_catalog.pg_authid" :
>
> Don't add a new line, and when the next step of information comes up
> append it to the existing line to get:
>
> INFO: analyzing "pg_catalog.pg_authid": scanned 1 of 1 pages, containing
> 5 live rows and 0 dead rows; 5 rows in sample, 5 estimated total rows
But then the line could only be pushed to the client *after* the analysis
of the table has finished, while with the current output you know what
postgres is currently doing, because you get "analyzing ..." *before*
the operation starts.
greetings, Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2007-06-11 19:24:51 | Selecting a constant question |
Previous Message | Joshua D. Drake | 2007-06-11 17:27:01 | Is this a feature? |