Tom Lane wrote:
> Andres Freund writes:
>> Afaik we don't have any debugging utility to dump the pg_filenode.map
>> contents?
>
> Hardly need one ... od -t d4 $PGDATA/global/pg_filenode.map
> is readable enough, though it does leave you still having to
> map the numeric OIDs back to names. The O
Florian Pflug wrote:
>> I used this to upgrade to 9.0.13, which indeed is fully compatible with
>> Debian. It started up like a charm. I can upgrade it to 9.1.9 now
>> (while I'm at it).
>Since you've been running with full_page_writes=off, I suggest you update
>to 9.1 by dumping and reloading y
On Apr9, 2013, at 19:56 , "Stephen R. van den Berg" wrote:
> Andres Freund wrote:
>> Afaik debian has never shipped 9.0 in any stable release at all. You can
>> use the packages provided by the postgres community though, they are
>> compatible:
>> http://wiki.postgresql.org/wiki/Apt
>
> I used th
Thanks, all of you, for all good advice and suggestions.
Andres Freund wrote:
>Afaik debian has never shipped 9.0 in any stable release at all. You can
>use the packages provided by the postgres community though, they are
>compatible:
>http://wiki.postgresql.org/wiki/Apt
I used this to upgrade to
Andres Freund writes:
> Afaik we don't have any debugging utility to dump the pg_filenode.map
> contents?
Hardly need one ... od -t d4 $PGDATA/global/pg_filenode.map
is readable enough, though it does leave you still having to
map the numeric OIDs back to names. The OIDs will be stable though.
Tom Lane wrote:
>"Stephen R. van den Berg" writes:
>> Tom Lane wrote:
>>> It's conceivable that updating to something more current than 9.0.4
>>> would get you out of this --- we've fixed quite a number of WAL replay
>>> bugs in the last two years.
>> I see that there is a 9.0.13, but that would
On 2013-04-09 19:30:38 +0200, Andres Freund wrote:
> On 2013-04-09 19:18:57 +0200, Stephen R. van den Berg wrote:
> > Tom Lane wrote:
> > >"Stephen R. van den Berg" writes:
> > >> Just today one of my systems experienced a kernel panic, and halted
> > >> abruptly.
> > >> Running Linux 3.1.9, Post
On 2013-04-09 13:34:41 -0400, Tom Lane wrote:
> "Stephen R. van den Berg" writes:
> > Tom Lane wrote:
> >> It's conceivable that updating to something more current than 9.0.4
> >> would get you out of this --- we've fixed quite a number of WAL replay
> >> bugs in the last two years.
>
> > I see t
"Stephen R. van den Berg" writes:
> Tom Lane wrote:
>> It's conceivable that updating to something more current than 9.0.4
>> would get you out of this --- we've fixed quite a number of WAL replay
>> bugs in the last two years.
> I see that there is a 9.0.13, but that would be a source upgrade, s
Andres Freund wrote:
>On 2013-04-09 18:21:20 +0200, Stephen R. van den Berg wrote:
>Thats an absolutely outdated version of 9.0. You shouldn't be running
>this in production.
Yes, well, it's one of those things. It got installed with Debian
and the automatic upgrade didn't upgrade it further, the
On 2013-04-09 19:18:57 +0200, Stephen R. van den Berg wrote:
> Tom Lane wrote:
> >"Stephen R. van den Berg" writes:
> >> Just today one of my systems experienced a kernel panic, and halted
> >> abruptly.
> >> Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
>
> >It's con
Joshua D. Drake wrote:
>full_page_writes = off is the problem.
>Turning this parameter off speeds normal operation, but might lead to
>either unrecoverable data corruption, or silent data corruption,
>after a system failure. The risks are similar to turning off fsync,
>though smaller, and it shoul
Tom Lane wrote:
>"Stephen R. van den Berg" writes:
>> Just today one of my systems experienced a kernel panic, and halted abruptly.
>> Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
>It's conceivable that updating to something more current than 9.0.4
>would get you out
"Stephen R. van den Berg" writes:
> Just today one of my systems experienced a kernel panic, and halted abruptly.
> Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
It's conceivable that updating to something more current than 9.0.4
would get you out of this --- we've fix
On 2013-04-09 18:21:20 +0200, Stephen R. van den Berg wrote:
> Just today one of my systems experienced a kernel panic, and halted abruptly.
> Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
Thats an absolutely outdated version of 9.0. You shouldn't be running
this in pro
On 04/09/2013 09:21 AM, Stephen R. van den Berg wrote:
-
Looking at global/11787, doesn't reveal any obvious corruption.
The server was running with:
synchronous_commit = off
full_page_writes = off
full_page_writes = off is the problem.
From the docs:
Turning th
Just today one of my systems experienced a kernel panic, and halted abruptly.
Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
The system was moderately active, i.e. about one commit per minute.
It is not a large problem if the last few commits would be gone.
Now, in rest
17 matches
Mail list logo
