*** This bug is a duplicate of bug 264336 ***
https://bugs.launchpad.net/bugs/264336
I am really sorry.
"sudo mv /etc/rc2.d/S19postgresql-8.3 /etc/rc2.d/S20postgresql-8.3" has fixed
my problem reliably.
I confused the output of sudo /etc/init.d/postgresql-8.3 status
"8.3 main 5432 on
*** This bug is a duplicate of bug 264336 ***
https://bugs.launchpad.net/bugs/264336
"sudo mv /etc/rc2.d/S19postgresql-8.3 /etc/rc2.d/S20postgresql-8.3" does
not reliably fix the problem (at the moment. I think I have been mangled
into another (new) problem, namely bug 264336.
When I reported
*** This bug is a duplicate of bug 264336 ***
https://bugs.launchpad.net/bugs/264336
Ah, that's interesting. Your problem is a duplicate of bug 264336.
However, I was unable so far to reproduce this. I just wonder why
starting postgresql a little later suddenly makes _more_ shared memory
avail
I have supplied the requested info
** Changed in: postgresql-8.3 (Ubuntu)
Status: Incomplete => New
--
postgresql-8.3 server does not start automatically
https://bugs.launchpad.net/bugs/387682
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I did.
There was some "Fail" text in the boot phase, but the text quickly
disappeard.
Now /etc/init.d/postgresql-8.3 status shows:
8.3 main 5432 down postgres /var/lib/postgresql/8.3/main
/var/log/postgresql/postgresql-8.3-main.log
I am pretty confident that this was not the ca
That's because postgresql itself creates the link priority as 19,
whereas your manual invocation uses "defaults" which equals to 20.
However, this by and large shouldn't make a difference. With the S19
links in place, can you please do a boot without "splash" (remove
"splash" in the grub menu after
