[HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-07 Thread KS
> -Original Message- > From: Mikheev, Vadim [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 04, 2001 3:37 AM > To: 'Tom Lane' > Subject: RE: [BUGS] Loosing files after backend crash > > > 1. Indices could be recreated with REINDEX or pg_class could > be queried > with seq scan (s

Re: [HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-05 Thread Vadim Mikheev
> > FATAL 2: XLogWrite: write request is past end of log" to syslog. Ok, I hope this one is fixed. Tom, please review changes. Konstantin, are you able to compile PG from CVS? To restart postmaster with current version... Vadim ---(end of broadcast)---

[HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-04 Thread Mikheev, Vadim
> Well, bad news. After a few more tries to crash the backend, the whole > postmaster crashed and didn't rise back. > It fails to start up reporting "Apr 4 18:53:05 wale > postgres[71618]: [9] > FATAL 2: XLogWrite: write request is past end of log" to syslog. Ok, this one is easy to fix. From

[HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-04 Thread Mikheev, Vadim
> Well, bad news. After a few more tries to crash the backend, the whole > postmaster crashed and didn't rise back. > It fails to start up reporting "Apr 4 18:53:05 wale > postgres[71618]: [9] > FATAL 2: XLogWrite: write request is past end of log" to syslog. Hmmm, the only XLogWrite startup p

[HACKERS] Re: [BUGS] Loosing files after backend crash

2001-04-04 Thread Tom Lane
KS <[EMAIL PROTECTED]> writes: > Well, bad news. After a few more tries to crash the backend, the whole > postmaster crashed and didn't rise back. > It fails to start up reporting "Apr 4 18:53:05 wale postgres[71618]: [9] > FATAL 2: XLogWrite: write request is past end of log" to syslog. Ugh.

[HACKERS] Re: [BUGS] Loosing files after backend crash

2001-04-03 Thread Tom Lane
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: >> Hmm. Maybe the WAL redo is messing things up?? > It could mess up pg_class content, but it never deletes > files (currently). I'm not convinced that any files have really been deleted. Maybe it's just that the pg_class entries are wrong, or even

[HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-03 Thread Mikheev, Vadim
> > How much time passed after sequence creation till crash? > >> > >> About 5-10 seconds. I opened a transaction, created a sequence, > >> created a temporary table with one column having NEXTVAL(seq) as > > ^ > >> default, inserted some data into the table, committed t

[HACKERS] Re: [BUGS] Loosing files after backend crash

2001-04-03 Thread Tom Lane
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: > Some more input from Konstantin (his answer to my message bounced > from bug-list -:)): > How much time passed after sequence creation till crash? >> >> About 5-10 seconds. I opened a transaction, created a sequence, >> created a temporary table wit

[HACKERS] RE: [BUGS] Loosing files after backend crash

2001-04-03 Thread Mikheev, Vadim
> Hm, that sounds like some sort of conflict with a temp table. Is it > possible that you have been using a temp table name that matches the > sequence name? Are there any pg_class entries whose names begin with > pg_temp, and if so could we see details on those too? Some more input from Konsta