Re: [GENERAL] Tablespace on Postgrsql

2013-07-25 Thread John R Pierce
On 7/24/2013 5:53 PM, devonline wrote: Our current database size is 1 Terabyte I would like to suggest that you pick a smaller system for your first experience with postgres, and work your way up to the big monster stuff after you've gained some experience. a terabyte database is a monste

Re: [GENERAL] Tablespace on Postgrsql

2013-07-25 Thread John R Pierce
On 7/25/2013 10:16 PM, Atri Sharma wrote: On Fri, Jul 26, 2013 at 7:21 AM, devonline wrote: >Thanks for the in formation. Can you please tell me what would be a scalable >architecture? (using pg_default) or separate custom tablespaces Putting too may tables in one tablespace can lead to confu

Re: [GENERAL] Tablespace on Postgrsql

2013-07-25 Thread Atri Sharma
On Fri, Jul 26, 2013 at 7:21 AM, devonline wrote: > Thanks for the in formation. Can you please tell me what would be a scalable > architecture? (using pg_default) or separate custom tablespaces Putting too may tables in one tablespace can lead to confusion, to say the least. Keeping logically s

Re: [GENERAL] Tablespace on Postgrsql

2013-07-25 Thread devonline
Thanks for the in formation. Can you please tell me what would be a scalable architecture? (using pg_default) or separate custom tablespaces -- View this message in context: http://postgresql.1045698.n5.nabble.com/Tablespace-on-Postgrsql-tp5765056p5765219.html Sent from the PostgreSQL - ge

Re: [GENERAL] Tablespace on Postgrsql

2013-07-25 Thread Luca Ferrari
On Thu, Jul 25, 2013 at 2:53 AM, devonline wrote: > Our current database size is > > 1 Terabyte > The idea behind tablespaces is to gain I/O scattering data (and therefore requests) across different devices. Therefore you have to identify first if your database can be "scattered" across different

Re: [GENERAL] Tablespace on Postgrsql

2013-07-24 Thread devonline
Our current database size is 1 Terabyte Thanks -- View this message in context: http://postgresql.1045698.n5.nabble.com/Tablespace-on-Postgrsql-tp5765056p5765082.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-genera

Re: [GENERAL] Tablespace on Postgrsql

2013-07-24 Thread John R Pierce
On 7/24/2013 1:32 PM, devonline wrote: We do have large Database with RAID 10. we do have Replication(Hot backup) . we would like to have the same on PostgreSQL when we migrate to PostgreSQL . Should we create separate tablespaces for Database and its objects or pg_default is fine as you have

Re: [GENERAL] Tablespace on Postgrsql

2013-07-24 Thread devonline
We do have large Database with RAID 10. we do have Replication(Hot backup) . we would like to have the same on PostgreSQL when we migrate to PostgreSQL . Should we create separate tablespaces for Database and its objects or pg_default is fine as you have mentioned earlier Thanks a lot Dev Onli

Re: [GENERAL] Tablespace on Postgrsql

2013-07-24 Thread John R Pierce
On 7/24/2013 12:31 PM, devonline wrote: I am new to PostgreSQL. I would like to know whether to use/pg_default/ Table space to create Database and its objetcs or to create custom Table space? I could not find what is recommended . tablespaces are usually only useful on very large scale se

[GENERAL] Tablespace on Postgrsql

2013-07-24 Thread devonline
I am new to PostgreSQL. I would like to know whether to use /pg_default/ Table space to create Database and its objetcs or to create custom Table space? I could not find what is recommended . Thanks Dev Online -- View this message in context: http://postgresql.1045698.n5.nabble.com/