Skip site navigation (1) Skip section navigation (2)

Re: store different tables in different locations

From: Julius Tuskenis <julius(at)nsoft(dot)lt>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: store different tables in different locations
Date: 2008-04-04 06:21:11
Message-ID: 47F5C8D7.9070904@nsoft.lt (view raw or flat)
Thread:
Lists: pgsql-admin
Hello,
1) To store tables in different locations use different tablespaces, 
witch can be stored in different locations in your hard drive. Same goes 
for the databases.

2)
a) Postgresql is fine data base management system, so I see no reasons 
why you should not use it.
b) I'm not sure I fully understand you on that one. You want to 
estimate, that after inserting some record into your database it will 
reach your maximum size? Any way I don't know how to do this...

Duan Ligong rašė:
> Hi, all
>
> I have several questions to bother you. :)
>
> 1 For postgresql, is it POSSIBLE to store different tables in 
> different locations where we specify? For one postgresql management 
> process,
> is it POSSIBLE to store different database in differentlocations
> where we specify?
>
> 2 Is it appropriate to use Postgresql to store data for the following 
> situation:
> The whole system consists of about 400 machines and I have to develop 
> a program collecting the information about capacity and performance 
> and networt setting and so on of each machines and displaying them for 
> the administrators and some related guys. Moreover, I have to store 
> some history data to display graphes
> and curvers. My design is as follows: one daemon process running on 
> each machine to collect data and send it to the database which is in 
> one specified machine.
> The bad thing is that the size of database is asked to be resricted in 
> 900MB for some reasons.
> The questions are:
> (a) Is it appropriate to use postgresql database in this case? If not, 
> any sugguestion will be appreciated.
>     In fact considered using common file to store data. but you know,
> it is possible that daemon processes on other 399 machines send data
> simultaneously, ...
>
> (b) It seems hard to estimate the maximum size of the database, 
> because frequently updating and inserting opreations will cause unused
> space not acclaiming in time and we have to routinely vaccum.
> Is there any good and easy, :) way to estimate the maximum size of
> postgresql database accurately?
>
> Best regards,
> Duan
>
>
> -- 
> Duan Ligong
> TEL   :  0561-75-1925-6201
>           800-81-569-6201
> E-Mail : l-duan(at)zd(dot)cnes(dot)jp(dot)nec(dot)com
>


-- 
Julius Tuskenis
Programuotojas
UAB nSoft
mob. +37068233050


In response to

Responses

pgsql-admin by date

Next:From: Duan LigongDate: 2008-04-04 07:32:23
Subject: Re: store different tables in different locations
Previous:From: Duan LigongDate: 2008-04-04 04:11:11
Subject: store different tables in different locations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group