From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: PRAGATI SAVAIKAR <pragati@phildigital.com>
To: pgsql-performance@postgresql.org
Subject: Re: Index File growing big.
Date: Wed, 26 Feb 2003 12:59:23 +0530
Message-ID: <200302261259.23604.mallah@trade-india.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet>
References: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet>
I remember this is your second posting for the same problem.
I hope you are aware that postgres can manage multiple databases that
lie in different partitions.
If its feasible for you you may think of moving the *big* tables in another
database which can be initialised in another partition. it depends on ur app
design as you will have to create a new db connection.
another possibility is to buy a new bigger hdd ofcourse ;-)
and migrate the data.
also i think the <tableid>.1 or <tableid>.2 are extensions of the
datafile not index files. index files have seperate id of their own.
pg_class have that id in relfilenode.
in case i am getting the problem wrong , my query is have you relocated the
index files also and created the symlinks ? (using ln -s)
Also 7.2.1 is too old an version to use in 7.2.x series 7.2.4 is latest
and in 7.3.x 7.3.2 is latest.
regds
mallah.
On Wednesday 26 February 2003 11:56 am, PRAGATI SAVAIKAR wrote:
> Hi !!
>
> We have "PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96"
> installed on Linux (RedHat 7.2)
> Our database size is 15 GB.
> Since the database size was increasing and was about to cross the actual
> Hard Disk parttion Size, we moved the datafiles (also the index files) to
> another partition and created link to them from the data directory.
> This was working fine.
> But what we found was , the index files(2 files) were not getting updated
> in the new partition, instead postgres had created another index file with
> name
> "tableID".1 in the original data directory. The size of this file was
> 356MB,
> The actual size of the data table is 1GB. and there were 2 indexes for the
> table. which were of size approximately=150MB.
>
> But after we created link, those 2 index files were not getting updated,
> instead the new file with ".1" extension got created in the data directory
> (old parttion) and the same is getting updated everyday.
>
> We dropped the table but the file with ".1" extension was not getting
> removed from data directory. We manually had to remove it.
>
> Can U please suggest some way to avoid the file getting created when we
> move the data file (along with the index files) to another partition.
>
>
> Thanks in Advance.
>
>
>
> Regards,
> Pragati.
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Regds
Mallah
----------------------------------------
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)
Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: mallah@trade-india.com, pragati@phildigital.com
Subject: Re: Index File growing big.
In-Reply-To: <200302261259.23604.mallah@trade-india.com>
References: <Pine.LNX.4.33.0302261155430.691-100000@minxserver.philnet> <200302261259.23604.mallah@trade-india.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox