| From: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Chen, Dongdong (GE Healthcare)" <DongdongChen(at)ge(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: need help for PostgreSQL consistency check mechanism |
| Date: | 2009-04-24 16:53:01 |
| Message-ID: | 92869e660904240953t2a93a61dp8cf0a503efb8a9aa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2009/4/24 Joshua D. Drake <jd(at)commandprompt(dot)com>
> On Fri, 2009-04-24 at 10:04 -0400, Alvaro Herrera wrote:
> > Chen, Dongdong (GE Healthcare) escribió:
> > >
> > > When the OS starts up, it wants to detect whether there is data loss
> > > in PostgreSQL from last shutdown, is there a method provided?
> >
> > Why would the OS want to do that?
>
> That doesn't make sense at all.
That is just a bad habit from MySQL world. People just don't understand that
all possible recovery is handled by postgres itself.
OTOH, there could be some consistency check method... If postgres had block-
or row-level checksums, this could do.
The best way I know is to do plain pg_dumpall. But this does not detect all
data corruptions.
--
Filip Rembiałkowski
JID,mailto:filip(dot)rembialkowski(at)gmail(dot)com
http://filip.rembialkowski.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Trutwin | 2009-04-24 17:01:52 | Selling an 8.1 to 8.3 upgrade |
| Previous Message | Erik Jones | 2009-04-24 16:31:41 | Re: OperationalError: FATAL: could not open file <filename>: Too many open files in system |