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