Re: [PERFORM] Clarification on using pg_upgrade

2016-06-14 Thread Tory M Blue
On Tue, Jun 14, 2016 at 2:03 PM, Jim Nasby wrote: > On 4/19/16 11:01 PM, Tory M Blue wrote: >> Slon is also starting to not be viable as it takes some indexes over >> 7 >> hours to complete. So this upgrade path seemed to really be nice. >>> >>> > >>> > >>> > If you're standing

Re: [PERFORM] Clarification on using pg_upgrade

2016-06-14 Thread Jim Nasby
On 4/19/16 11:01 PM, Tory M Blue wrote: >> Slon is also starting to not be viable as it takes some indexes over 7 >> hours to complete. So this upgrade path seemed to really be nice. > > > If you're standing up a new replica from scratch on the latest version, I'm > not really sure why that matt

Re: [PERFORM] pg_database_size

2016-06-14 Thread Jim Nasby
On 6/4/16 3:10 AM, Venkata Balaji N wrote: On Sat, Jun 4, 2016 at 5:35 PM, sangeetha mailto:tune2san...@gmail.com>> wrote: SELECT pg_database_size('DB1') takes 60ms for 7948 kB size DB. Is there any way to reduce the time taken or any other ways to find data base size? What is th