POstgreSQL Tablespace deletion issue

From: "Vishnu S(dot)" <vishnu(dot)s(at)nestgroup(dot)net>
To: <vibhor(dot)aim(at)gmail(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: POstgreSQL Tablespace deletion issue
Date: 2011-10-18 06:16:47
Message-ID: D0124DE0373A744CA8192AFA82C8311707D17CF1@mail-4.tvm.nestgroup.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

HI,

I am using PostgreSQL 8.4 in windows XP. Also using Slony-I for
implementing master/slave support. I have a data base with some tables
and a table space with some other tables in another location. My issue
is that after a 30 days continuous run, some of the files in the
PostgreSQL table space get deleted. The modification that I had made
recently is that, I have created indexes on some of the tables in the
table space. But the indexes are actually created on the default table
space, not in the table space where the tables resides. Is any problem
in it? Note that there is antivirus or clan up applications running on
the system. The only thing that we have done is that , the machine has
restarted 5 - 6 times without stopping the PostgreSQL server. (The
PostgreSQL server running on 5432 post is a custom database server
created and not the default PostgreSQL server coming when PostgreSQL is
installed.) Is there any chances for failing the crash recovery? Is
there any chance for deleting the table space files, if the crash
recovery is failed ? How can we avoid this ?

Thanks & Regards,

Vishnu S

***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

Browse pgsql-general by date

  From Date Subject
Next Message Mark Priest 2011-10-18 06:52:41 Out of Memory Error on Insert
Previous Message Evan Martin 2011-10-18 04:57:36 Plans to fix table inheritance caveats