http://bugzilla.novell.com/show_bug.cgi?id=623902
http://bugzilla.novell.com/show_bug.cgi?id=623902#c3
Reinhard Max
[1] The only commandline arguments where the name of a local db. No host, users, etc. That shouldn't matter anyway, since it crashed in readline.
The piece of code that crashes isn't necessarily the piece of code that contains the bug. E.g. readline may crash on memory corruption caused by an unrelated command line switch.
[2] It happened after some time. Perhaps an hour.
Can you approximate how many SQL commands you had executed between the process start and the crash?
[3] UNfortunately, I don't recall exactly what they were but they were fairly long (3-10 line) sql queries. They didn't get saved to ~/.psql_history, of course. ;-)
If you still have the core file, you may find the SQL strings in there.
I should also note that postmaster has *crashed* on my machine since upgrading to openSUSE 11.3 (same config files, same database, same everything) at least 5 times in the last 36 hours.
What openSUSE and PostgreSQL versions were you using before?
Eventually, I figured out that it was getting killed by the oom handler,
The oom handler kills the first process that requests memory when no more is available, but that's not necessarily the process that has actually caused the machine to be short on memory.
despite being configured to only use 0.5G (of 4G) of RAM.
There are several options in postgresql.conf that control different aspects of the PosrgreSQL server's memory usage. Which one are you referring to?
I cannot be sure but I *think* the autovacuum handler was what was running at the time.
Well, if the machine is nearly oom already and then autovacuum kicks in requesting some more memory, it might get killed although not being the actual cause for the memory shortage. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.