When I ran that command (select * from pg_stat_activity"), it returned the first six lines of the scripts. I'm fairly sure it has gotten a bit beyond that (been running over 24 hours now, and the size has increased about 300 GB). Am I missing something for it to tell me what the last line processed was?
I didn't do any profiling (postgres newbie here). All of the updates are fairly straightforward and only hit a single table. They are updating a single column based upon a "where between" clause which hits an index. I did run a single one initially, and then a group of about 10k to make sure they were behaving properly before launching the rest of the pile... This is my first postgres project. It's a table of the complete IPV4 address space. Trying out postgres because the MySQL (actually MariaDB) attempt was not scaling well. On Tue, Nov 26, 2013 at 11:20 AM, Vick Khera <vi...@khera.org> wrote: > Connect to the DB and run "select * from pg_stat_activity" to see what > specific query your other connection is running. Then find that in your > file to see how far it has progressed. > > I hope you profiled your queries to make sure they run fast before you > started. :) > > > On Tue, Nov 26, 2013 at 10:28 AM, Joey Quinn <bjquinn...@gmail.com> wrote: > >> I have a fairly large table (4.3 billion rows) that I am running an >> update script on (a bit over 127 thousand individual update queries). I am >> using the gui. It has been running for about 24 hours now. Is there any >> good way to gauge progress (as in, how many of the individual update >> queries have finished)? >> >> >> >
