| From: | "Ramachandran S" <nic(dot)srama(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #5612: Database Integrity |
| Date: | 2010-08-11 09:36:31 |
| Message-ID: | 201008110936.o7B9aVUI042007@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5612
Logged by: Ramachandran S
Email address: nic(dot)srama(at)gmail(dot)com
PostgreSQL version: 8.4
Operating system: Ubuntu
Description: Database Integrity
Details:
I have observed that if a table exceeds size (default installation) 1 GB.
The table when it exceeds 1 GB a file is created say 1811(table) with 1811.1
and further records added are insertted into this file. My Question if I
remove the file 1811.1 say still database is starting up? I will never
know that such a file existed nad remved and data of 1811 is also availble?
How can stop the start the database when such situation recur. pgfsck was
available 8.2
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-11 13:32:59 | Re: BUG #5604: Setting NOT NULL on inherited column turns to real column in dump |
| Previous Message | Mark Kirkwood | 2010-08-11 02:55:35 | Re: Measuring execution time |