i had a lot of debugging enabled.  i went to create an index, and pgsql 
dumped on me.  i tried restarting several times - no luck.

starting postgresql gives:

LOG:  database system shutdown was interrupted at 2004-07-16 01:11:56 EDT
LOG:  checkpoint record is at 0/53A3FC0
LOG:  redo record is at 0/53A3FC0; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 44321; next oid: 111535
LOG:  database system was not properly shut down; automatic recovery in 
progress
LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment 
5, offset 3817472
LOG:  redo is not required
                                                            [  OK  ]
# PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
LOG:  startup process (pid 16068) was terminated by signal 6
LOG:  aborting startup due to startup process failure

this is 7.3.3 (PGDG rpm's) on red hat 7.2


Fri, 16 Jul 2004 01:32:01 -0400
lists <lists01@dds.uconn.edu>
XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
thank you for replying.

Alvaro Herrera wrote:
>>LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment 
>>5, offset 3817472
>>LOG:  redo is not required
>>PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
>>LOG:  startup process (pid 16068) was terminated by signal 6
>>LOG:  aborting startup due to startup process failure
>>
>>this is 7.3.3 (PGDG rpm's) on red hat 7.2
> 
> Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
> 7.3.4.

do you know if there are rpm's for RH7.2 available?

to get the data back, is it a matter of just upgrading and starting the 
db (ie will it perform recovery)?


thanks

Fri, 16 Jul 2004 01:55:13 -0400
lists <lists01@dds.uconn.edu>
Re: XLogWrite: write request 0/53A4000 is past end of log
On Fri, Jul 16, 2004 at 01:32:01AM -0400, lists wrote:

> LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment 
> 5, offset 3817472
> LOG:  redo is not required
> PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
> LOG:  startup process (pid 16068) was terminated by signal 6
> LOG:  aborting startup due to startup process failure
> 
> this is 7.3.3 (PGDG rpm's) on red hat 7.2

Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
7.3.4.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Al principio era UNIX, y UNIX hablï¿½ y dijo: "Hello world\n".
No dijo "Hello New Jersey\n", ni "Hello USA\n".


Fri, 16 Jul 2004 01:56:47 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl>
Re: XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
  >>LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment
>>5, offset 3817472
>>LOG:  redo is not required
>>PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
>>LOG:  startup process (pid 16068) was terminated by signal 6
>>LOG:  aborting startup due to startup process failure
>>
>>this is 7.3.3 (PGDG rpm's) on red hat 7.2
> 
> 
> Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
> 7.3.4.

That won't help him start up his DB though will it?  It will just 
prevent the problem in the future?  Is it the same fix as for me? 
Appending zeros to a file?

Chris


Fri, 16 Jul 2004 14:09:33 +0800
Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: XLogWrite: write request 0/53A4000 is past end of log
On Fri, Jul 16, 2004 at 01:55:13AM -0400, lists wrote:
> thank you for replying.
> 
> Alvaro Herrera wrote:
> >>LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment 
> >>5, offset 3817472
> >>LOG:  redo is not required
> >>PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
> >>LOG:  startup process (pid 16068) was terminated by signal 6
> >>LOG:  aborting startup due to startup process failure
> >>
> >>this is 7.3.3 (PGDG rpm's) on red hat 7.2
> >
> >Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
> >7.3.4.
> 
> do you know if there are rpm's for RH7.2 available?

No idea, sorry.

> to get the data back, is it a matter of just upgrading and starting the 
> db (ie will it perform recovery)?

That should do.

Depending on how much you value your data, however, it might be
advisable to make a backup of the data directory just in case ...

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Pensar que el espectro que vemos es ilusorio no lo despoja de espanto,
sï¿½lo le suma el nuevo terror de la locura" (Perelandra, CSLewis)


Fri, 16 Jul 2004 02:10:34 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl>
Re: XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
On Fri, Jul 16, 2004 at 02:09:33PM +0800, Christopher Kings-Lynne wrote:
>  >>LOG:  ReadRecord: unexpected pageaddr 0/33A4000 in log file 0, segment
> >>5, offset 3817472
> >>LOG:  redo is not required
> >>PANIC:  XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
> >>LOG:  startup process (pid 16068) was terminated by signal 6
> >>LOG:  aborting startup due to startup process failure
> >>
> >>this is 7.3.3 (PGDG rpm's) on red hat 7.2
> >
> >
> >Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
> >7.3.4.
> 
> That won't help him start up his DB though will it?

AFAIU it should ...

> It will just prevent the problem in the future?  Is it the same fix as
> for me?  Appending zeros to a file?

As far as I remember, your problem was much worse ... This is a strange
bug where the Xlog code would refuse to replay a record that starts just
at the start of the segment.  A later version deals with this situation
correctly.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Este mail se entrega garantizadamente 100% libre de sarcasmo.


Fri, 16 Jul 2004 02:13:25 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl>
Re: XLogWrite: write request 0/53A4000 is past end of log 0/53A4000
lists <lists01@dds.uconn.edu> writes:
> Alvaro Herrera wrote:
>>> this is 7.3.3 (PGDG rpm's) on red hat 7.2
>> 
>> Get 7.3.6 and try again.  IIRC this is a known bug that was repaired in
>> 7.3.4.

> to get the data back, is it a matter of just upgrading and starting the 
> db (ie will it perform recovery)?

Yes.  There's nothing wrong with your data, it's just a corner case that
was not correctly handled by the recovery code in 7.3.3.

You could actually use any version 7.3.4-7.3.6, but you might as well go
to 7.3.6 while you're at it.

			regards, tom lane

Fri, 16 Jul 2004 09:58:56 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: XLogWrite: write request 0/53A4000 is past end of log 