Re: postgresql crushed with XLogWrite error - Mailing list pgsql-admin

From Tsirkin Evgeny
Subject Re: postgresql crushed with XLogWrite error
Date
Msg-id opr1a4qaq4jbdarf@localhost
Whole thread Raw
In response to Re: postgresql crushed with XLogWrite error  (Andrew Sullivan <andrew@libertyrms.info>)
Responses Re: postgresql crushed with XLogWrite error
List pgsql-admin
Probably a dumm question ,but it is better to ask then be sorry.
Nothing is changed in config files ,so i am extractiing
the binary from rpm ,copy it to the place and start the server,right?
And thanks again!
On Mon, 5 Jan 2004 09:09:55 -0500, Andrew Sullivan
<andrew@libertyrms.info> wrote:

> On Mon, Jan 05, 2004 at 04:07:34PM +0200, Tsirkin Evgeny wrote:
>> Thanks!
>> Now another two questions:
>> Is there any official bug report on this that i can show to
>> my boss?
>
> Yes, it's in the release notes.  IIRC, there were like 24 or 48 hours
> between the releases because of this.  Tom Lane occasionally beats
> himself up about the bug on-list.
>
>> Should i upgrade to 7.3.4 to fix that bug or it is better to get newly
>> version?
>
> You can upgrade to the lastest 7.3.x release by just dropping the new
> binary in place, IIRC -- read the release notes.  In any case, you'll
> need to get some version of 7.3 running first.
>
> A
>
> ----
> Andrew Sullivan                         204-4141 Yonge Street
> Afilias Canada                        Toronto, Ontario Canada
> <andrew@libertyrms.info>                              M2P 2A8
>                                          +1 416 646 3304 x110
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster




pgsql-admin by date:

Previous
From: "Glenn Wiorek"
Date:
Subject: Re: what is the cause that scan type is showing as 'seq scan' after
Next
From: Andrew Sullivan
Date:
Subject: Re: postgresql crushed with XLogWrite error