On 9/4/14 4:23 PM, Pavel Stehule wrote:
It is little bit hard to read.
maybe better be more verbose - and it can be in alone function, because
it is analyze only
if (stage == -1)
{
for (i = 0; i 3; i++)
{
puts(gettext(stage_messages[i]));
executeCommand(conn,
2014-09-12 3:44 GMT+02:00 Peter Eisentraut pete...@gmx.net:
On 9/4/14 4:23 PM, Pavel Stehule wrote:
It is little bit hard to read.
maybe better be more verbose - and it can be in alone function, because
it is analyze only
if (stage == -1)
{
for (i = 0; i 3; i++)
{
2014-09-04 5:36 GMT+02:00 Peter Eisentraut pete...@gmx.net:
On Mon, 2014-05-19 at 13:51 -0400, Peter Eisentraut wrote:
On 5/18/14, 3:52 AM, Pavel Stehule wrote:
I am looking on --analyze-in-stages option. If I understand well,
motivation for this option is a get some minimal statistic
On Mon, 2014-05-19 at 13:51 -0400, Peter Eisentraut wrote:
On 5/18/14, 3:52 AM, Pavel Stehule wrote:
I am looking on --analyze-in-stages option. If I understand well,
motivation for this option is a get some minimal statistic for databases
in minimal time. But when I tested, I found so
On 5/18/14, 3:52 AM, Pavel Stehule wrote:
Hello
I am looking on --analyze-in-stages option. If I understand well,
motivation for this option is a get some minimal statistic for databases
in minimal time. But when I tested, I found so iterations are per
databases, not per stages - some first
Hello
I am looking on --analyze-in-stages option. If I understand well,
motivation for this option is a get some minimal statistic for databases in
minimal time. But when I tested, I found so iterations are per databases,
not per stages - some first database get a maximum statistics and second
