| From: | jdassen(at)cistron(dot)nl (J(dot)H(dot)M(dot) Dassen (Ray)) |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: md_open problem |
| Date: | 2001-01-26 14:23:58 |
| Message-ID: | slrn973229.tim.jdassen@odin.cistron-office.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Rommel B. Abaya <rommel(dot)abaya(at)ramcargroup(dot)com> wrote:
>this has occured to me quite often and im out of solution for this. how do
>you address an md_open() problem in PostgreSQL? It occurs everytime the
>Linux box goes on power failure while transactions are being commited to
>the database.
>i also try dropping the tables but i get the same md_open error.
I'm not sure I recall the exact sequence to fix things, but I believe it is
- touch(1) the data/base/<name>/<tablename> PostgreSQL is complaining about
into existence
- drop the table
- recreate the table
HTH,
Ray
--
Brought to you by Microsoft .NOT technology: just say No.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | geny.matsui | 2001-01-26 16:42:34 | How many memory a backend process use ? |
| Previous Message | Rommel B. Abaya | 2001-01-26 01:46:20 | md_open problem |