Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-08 Thread Christopher Browne
[EMAIL PROTECTED] (Andrew Sullivan) writes: > On Mon, Jan 05, 2004 at 07:35:16PM +0200, Tsirkin Evgeny wrote: >> On Mon, 5 Jan 2004 11:23:08 -0500, Andrew Sullivan >> <[EMAIL PROTECTED]> wrote: >> >> I want to keep my configs.Of course i can save my postgresql.conf >> (and other files that i chan

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
On Mon, 5 Jan 2004 12:39:20 -0500, Andrew Sullivan <[EMAIL PROTECTED]> wrote: The only things that should make a difference to you should be in the /etc directory, assuming the RPM follows the filesystem standard (I believe it does). It does not ,rpm puts the staff in /var/lib My suggestion is t

[ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
Hello dear list! I am using postgresql 7.3.3 .Last night the errors occured. Since then I can't start the postgresql !We are recovering from the type by now ,but what happened?Is that a known bug?What to do next time? The last change I made was that: syslog=1 log_min_error_statement log_timestamp =

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Andrew Sullivan
On Mon, Jan 05, 2004 at 07:35:16PM +0200, Tsirkin Evgeny wrote: > On Mon, 5 Jan 2004 11:23:08 -0500, Andrew Sullivan > <[EMAIL PROTECTED]> wrote: > > I want to keep my configs.Of course i can save my postgresql.conf > (and other files that i changed and don't currently remember) > to another loca

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
On Mon, 5 Jan 2004 11:23:08 -0500, Andrew Sullivan <[EMAIL PROTECTED]> wrote: I want to keep my configs.Of course i can save my postgresql.conf (and other files that i changed and don't currently remember) to another location and then put it back in place of what rpm will put ,but as i said ,i do

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Andrew Sullivan
On Mon, Jan 05, 2004 at 04:48:00PM +0200, Tsirkin Evgeny wrote: > 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! If you're upgradi

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
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 <[EMAIL PROTECTED]> wrote: On Mon, Ja

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Andrew Sullivan
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 occa

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
Thanks! Now another two questions: Is there any official bug report on this that i can show to my boss? Should i upgrade to 7.3.4 to fix that bug or it is better to get newly version? What i need is to restore my corrupted db from the tape ,upgrade postgresql (say from rpm) and just start the serv

Re: [ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Andrew Sullivan
On Mon, Jan 05, 2004 at 02:14:37PM +0200, Tsirkin Evgeny wrote: > Hello dear list! > I am using postgresql 7.3.3 .Last night the errors occured. ^ > by now ,but what happened?Is that a known bug?What to do next time? Yes, it's a known bug, and is the very reason 7.

[ADMIN] postgresql crushed with XLogWrite error

2004-01-05 Thread Tsirkin Evgeny
Hello dear list! I am using postgresql 7.3.3 .Last night the errors occured. Since then I can't start the postgresql !We are recovering from the type by now ,but what happened?Is that a known bug?What to do next time? The last change I made was that: syslog=1 log_min_error_statement log_tim