From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | Bosco Rama <postgres(at)boscorama(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why are pg_restore taking that long ? |
Date: | 2012-05-20 16:22:22 |
Message-ID: | 20669.1337530942@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> ... Notice that pg_backup_archiver.c and
> pg_backup_tar.c use an inconsistent log level for this same message,
> which might explain where you saw the message previously.
Seems like that ought to be fixed.
> ... Or change this bit in pg_restore.c to assign a 2
> instead of a 1:
>
> case 'v': /* verbose */
> opts->verbose = 1;
> break;
"verbose" is used as a boolean, so that wouldn't actually help.
> It'd sure be nice to have these programs allow "-vvvv" style switches
> to signify cranking up the debugLevel, unless I'm missing some other
> way to do so.
Yeah. ahlog() also pays attention to a "debugLevel" value, but AFAICS
that's totally vestigial with no way to set it. It would likely be a
worthwhile activity to rationalize these things into a single
maximum-message-level value that could be ratcheted up with multiple -v
switches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Kupershmidt | 2012-05-20 17:10:52 | Re: Why are pg_restore taking that long ? |
Previous Message | Poul Møller Hansen | 2012-05-20 15:39:31 | Re: Why are pg_restore taking that long ? |