Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Peter Geoghegan
On Wed, Aug 26, 2015 at 3:36 PM, Tomas Vondra wrote: >> But I guess the answer is, no real way to tell what the box is doing >> when it's creating an index. Yes there was a lock, no I could not find a >> way to see how it's progressing so there was no way for me to gauge when >> it would be done.

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tomas Vondra
On 08/26/2015 10:26 PM, Tory M Blue wrote: the table is 90GB without indexes, 285GB with indexes and bloat, The row count is not actually completing.. 125Million rows over 13 months, this table is probably close to 600million rows. You don't need to do SELECT COUNT(*) if you only need an

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tomas Vondra
Hi, On 08/26/2015 11:53 PM, Tory M Blue wrote: On Wed, Aug 26, 2015 at 2:45 PM, Qingqing Zhou mailto:zhouqq.postg...@gmail.com>> wrote: On Wed, Aug 26, 2015 at 1:26 PM, Tory M Blue mailto:tmb...@gmail.com>> wrote: > > Right now the 100% cpu process which is this index is only us

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tory M Blue
On Wed, Aug 26, 2015 at 2:45 PM, Qingqing Zhou wrote: > On Wed, Aug 26, 2015 at 1:26 PM, Tory M Blue wrote: > > > > Right now the 100% cpu process which is this index is only using 3.5GB > > and has been for the last 15 hours > > > > If 100% cpu, you can do 'sudo perf top' to see what the CPU is

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Qingqing Zhou
On Wed, Aug 26, 2015 at 1:26 PM, Tory M Blue wrote: > > Right now the 100% cpu process which is this index is only using 3.5GB > and has been for the last 15 hours > If 100% cpu, you can do 'sudo perf top' to see what the CPU is busy about. Regards, Qingqing -- Sent via pgsql-performance mail

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tory M Blue
On Wed, Aug 26, 2015 at 12:36 PM, Igor Neyman wrote: > > > > > *From:* Tory M Blue [mailto:tmb...@gmail.com] > *Sent:* Wednesday, August 26, 2015 3:26 PM > *To:* Igor Neyman > *Cc:* pgsql-performance > *Subject:* Re: [PERFORM] Index creation running now for 14 hours

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Igor Neyman
From: Tory M Blue [mailto:tmb...@gmail.com] Sent: Wednesday, August 26, 2015 3:26 PM To: Igor Neyman Cc: pgsql-performance Subject: Re: [PERFORM] Index creation running now for 14 hours On Wed, Aug 26, 2015 at 12:18 PM, Igor Neyman mailto:iney...@perceptron.com>> wrote: From:

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tory M Blue
*Subject:* [PERFORM] Index creation running now for 14 hours > > > > I'm running 9.3.4 with slon 2.2.3, I did a drop add last night at 9pm, it > started this particular tables index creation at 10:16pm and it's still > running. 1 single core is at 100% (32 core box) and

Re: [PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Igor Neyman
From: pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Tory M Blue Sent: Wednesday, August 26, 2015 3:14 PM To: pgsql-performance Subject: [PERFORM] Index creation running now for 14 hours I'm running 9.3.4 with slon 2.2.3, I did a dro

[PERFORM] Index creation running now for 14 hours

2015-08-26 Thread Tory M Blue
I'm running 9.3.4 with slon 2.2.3, I did a drop add last night at 9pm, it started this particular tables index creation at 10:16pm and it's still running. 1 single core is at 100% (32 core box) and there is almost zero I/O activity. CentOS 6.6 16398 | clsdb | 25765 | 10 | postgres | slon.