| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Ramachandran S <nic(dot)srama(at)gmail(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5612: Database Integrity |
| Date: | 2010-08-11 17:38:01 |
| Message-ID: | 1281548220-sup-3350@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from Ramachandran S's message of mié ago 11 05:36:31 -0400 2010:
> 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?
You're not supposed to mess with the underlying files. If you randomly
delete files, it's your problem.
No, we don't have pgfsck.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott | 2010-08-11 17:41:45 | BUG #5613: cannot delete |
| Previous Message | Brian Ceccarelli | 2010-08-11 15:50:25 | Re: BUG #5611: SQL Function STABLE promoting to VOLATILE |