From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Craig Ringer <craig@2ndquadrant.com>
To: Taiki Kondo <tai-kondo@yk.jp.nec.com>
Cc: andres@anarazel.de <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Akio Iwaasa <aki-iwaasa@vt.jp.nec.com>
Cc: Jan Urbański <wulczer@wulczer.org>
Subject: Re: [Proposal] Progress bar for pg_dump/pg_restore
Date: Mon, 22 Jun 2015 18:06:06 -0500
Message-ID: <558894DE.20807@BlueTreble.com> (raw)
In-Reply-To: <CAMsr+YEwOVwVoibmCAEnJc5J_0gi9fD0kzqfVNZMZObcozdKtQ@mail.gmail.com>
References: <12A9442FBAE80D4E8953883E0B84E08855C876@BPXM01GP.gisp.nec.co.jp>
<20150612134801.GF28424@awork2.anarazel.de>
<12A9442FBAE80D4E8953883E0B84E08856D696@BPXM01GP.gisp.nec.co.jp>
<CAMsr+YEwOVwVoibmCAEnJc5J_0gi9fD0kzqfVNZMZObcozdKtQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 6/21/15 9:45 PM, Craig Ringer wrote:
>> And, I also understood your concern about "CREATE INDEX", but we have no way to get progress information of "CREATE INDEX".
>> >At present, I think it may be good to refer to the same time as estimated time to execute "COPY TO".
> You could probably get a handwave-quality estimate by looking at the
> average column widths for the cols included in the index plus the
> number of tuples in the table. It'd be useless for expression indexes,
> partial indexes, etc, but you can't have everything...
Jan Urbański demonstrated[1] getting progress stats for long running
queries[2] at pgCon 2013. Perhaps some of that code would be useful here
(or better yet perhaps we could include at least the measuring portion
of his stuff in core... ;)
[1] https://www.pgcon.org/2013/schedule/events/576.en.html
[2] https://github.com/wulczer/pg-progress
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, craig@2ndquadrant.com, tai-kondo@yk.jp.nec.com, andres@anarazel.de, aki-iwaasa@vt.jp.nec.com, wulczer@wulczer.org
Subject: Re: [Proposal] Progress bar for pg_dump/pg_restore
In-Reply-To: <558894DE.20807@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox