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

Re: Tablespace files deleted in continuous run

From: "Nathan M(dot) Davalos" <n(dot)davalos(at)sharedmarketing(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Tablespace files deleted in continuous run
Date: 2011-10-13 15:49:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
I generally use Ontrack EasyRecovery Professional for recovering deleted
or data sitting in bad sectors from hard drives in windows. It's not
free, but it works really well. 


I have had issues with Symantec BackupExec causing PostgreSQL to panic
and shutdown when data is being inserted into tables during a backup.
Might check to see if any backups were in progress at the time if you
are doing file system backups of your PostgreSQL directory.



From: pgsql-bugs-owner(at)postgresql(dot)org
[mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Vishnu S.
Sent: Thursday, October 13, 2011 7:53 AM
To: pgsql-bugs(at)postgresql(dot)org
Subject: [BUGS] Tablespace files deleted in continuous run






I am using PostgreSQL 8.4 in windows.  I have  created a database and
some tables on it. Also created a table space and some tables in it. My
application inserts data into these tables in every second. The
application is a continuous running application. My issue is that after
a 20-30 days continuous run ( Machine logged off  2 times), some of the
files in the  \16384 folder of newly created table space are dropped
automatically. Can  you tell me the reason for this.?  How can we
recover from this?



I have a task that delete the data(only data stored in table) from the
tables in the tablespace in certain interval.  Is there any problem
related to this?

Can you tell me the reason for 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.

In response to

pgsql-bugs by date

Next:From: Andrew KerrDate: 2011-10-13 16:28:15
Subject: BUG #6254: COPY ... TO .. CSV sometimes doesn't escape strings
Previous:From: Kevin GrittnerDate: 2011-10-13 14:39:58
Subject: Re: Tablespace files deleted in continuous run

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