From: | "Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca> |
---|---|
To: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "Kelly Harmon" <kelly(dot)harmon(at)byers(dot)com> |
Subject: | Re: Accessing Database files on a "read-only" medium...like a CD. |
Date: | 2001-10-08 04:23:18 |
Message-ID: | 06d801c14fb0$f7263800$5dd9fea9@gunn |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kelly Harmon <kelly(dot)harmon(at)byers(dot)com> wrote in message news:9pr7f7$k0j$1(at)news(dot)tht(dot)net(dot)(dot)(dot)
> SO...I dug around through the code a little and found where the error was
> coming from and changed the code so that if the open attempt with O_RDWR
> fails, the code tries again with O_RDONLY. This was in md.c...in the mdopen
> function.
>
> This did work....I was then able to open the database and do queries and
> whatnot. Trying to insert into the table didn't give any errors...until I
> tried to select the record back out, at which time it started giving me
> errors such as:
>
> ERROR: cannot write block 7548 of pole: Permission denied
>
> At that point, it seems that your screwed...in that even if you shut down
> postgres and restart it, somewhere it knows that that database has data that
> needs to be written to disk, and it refuses to continue until it does so.
Isn't it the WAL who 'remembers' this info?
--
Serguei A. Mokhov
From | Date | Subject | |
---|---|---|---|
Next Message | Kelly Harmon | 2001-10-08 07:46:15 | Re: Accessing Database files on a "read-only" medium...like a CD. |
Previous Message | Kelly Harmon | 2001-10-08 03:46:14 | Accessing Database files on a "read-only" medium...like a CD. |