Re: Current CVS tip segfaulting

> > Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> > >>> In current (as of a couple hours ago) clean CVS tip sources, without any
> > >>> of my local changes, I'm getting a postmaster segfault when trying to
> > >>> connect to a non existant database.
> >
> > Alvaro, did you figure this out?  I've been mostly distracted for the
> > past week ...
>
> No.  I still see the failure on my platform but I don't know what to
> attribute it to.

I also have that for a database installation from CVS on April 17.

It also leaves the server in some incoherent state:

Apr 30 17:58:22 sablons postgres[31629]: [31-1] FATAL:  database "toto" does not exist
Apr 30 17:58:22 sablons postgres[31604]: [31-1] LOG:  server process (PID 31629) was terminated by signal 11
Apr 30 17:58:22 sablons postgres[31604]: [32-1] LOG:  terminating any other active server processes
Apr 30 17:58:22 sablons postgres[31532]: [31-1] WARNING:  terminating connection because of crash of another server
process
Apr 30 17:58:22 sablons postgres[31532]: [31-2] DETAIL:  The postmaster has commanded this server process to roll back
thecurrent transaction and exit, because another server
 
Apr 30 17:58:22 sablons postgres[31532]: [31-3]  process exited abnormally and possibly corrupted shared memory.
Apr 30 17:58:22 sablons postgres[31532]: [31-4] HINT:  In a moment you should be able to reconnect to the database and
repeatyour command.
 
Apr 30 17:58:22 sablons postgres[31604]: [33-1] LOG:  all server processes terminated; reinitializing
Apr 30 17:58:22 sablons postgres[31630]: [34-1] LOG:  database system was interrupted at 2004-04-30 17:54:56 CEST
Apr 30 17:58:22 sablons postgres[31630]: [35-1] LOG:  checkpoint record is at 0/B486F30
Apr 30 17:58:22 sablons postgres[31630]: [36-1] LOG:  redo record is at 0/B486F30; undo record is at 0/0; shutdown
TRUE
Apr 30 17:58:22 sablons postgres[31630]: [37-1] LOG:  next transaction ID: 10769; next OID: 123703
Apr 30 17:58:22 sablons postgres[31630]: [38-1] LOG:  database system was not properly shut down; automatic recovery in
progress
Apr 30 17:58:22 sablons postgres[31630]: [39-1] LOG:  redo starts at 0/B486F70Apr 30 17:58:22 sablons postgres[31630]:
[40-1]PANIC:  could not create relation 123703/16660: No such file or directory
 
Apr 30 17:58:22 sablons postgres[31604]: [34-1] LOG:  startup process (PID 31630) was terminated by signal 6
Apr 30 17:58:22 sablons postgres[31604]: [35-1] LOG:  aborting startup due to startup process failure

So it is not a "clean" coredump, if some may be;-)

-- 
Fabien Coelho - coelho@cri.ensmp.fr