new kernel breaks postgresql on postgresql upgrade
 

The transition from postgresql 8.4 to postgresql 9.1 almost worked over
here except for a little matter of the linux kernel's shm value. This
broke when I was involved with pg_upgradecluster and afterwards 9.1
wouldn't start. End result, all of postgresql has been removed from this
machine. Fortunately mysql either has no shm variable size dependency or
is a little better at handling it or a little more reasonable in its
requirements.



----------------------------------------------------------------
Microsoft: It never looses its suction.

Jude
<jdashiel-at-shellworld-dot-net>
<http://www.shellworld.net/~jdashiel/nj.html>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: alpine.BSF.2.01.1207010444260.96196@freire1.furyyj beyq.arg">http://lists.debian.org/alpine.BSF.2.01.1207010444260.96196@freire1.furyyj beyq.arg

new kernel breaks postgresql on postgresql upgrade
 

On Sun, Jul 01, 2012 at 04:49:32AM -0400, Jude DaShiell wrote:
> The transition from postgresql 8.4 to postgresql 9.1 almost worked over
> here except for a little matter of the linux kernel's shm value. This
> broke when I was involved with pg_upgradecluster and afterwards 9.1
> wouldn't start. End result, all of postgresql has been removed from this
> machine.

Ouch!! That should not have happened. I vaguely remember running into
the same problem.

Adding: "kernel.shmmax = 40000000" into /etc/sysctl.conf fixed it for
me. Have you lost all your data?

This was a while ago, but because I'd botched a postgresql upgrade at
sometime in the past I was extra careful to double check each step.

It is essential to read all files in /usr/share/doc/postgresql*
on a major version upgrade.

My upgrade from postgresql 8.4 to postgresql 9.1 was OK once I knew
about the "kernel.shmmax" variable.

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120701230527.GF15677@tal

new kernel breaks postgresql on postgresql upgrade
 

I was fortunate in that I hadn't put any data into that database system
yet. The 40,000,000 value for shm is higher than the 34 million and
change value that postgresql was using before and that would explain why
this failure happened. However, it will be a good idea to fix the
postgresql 9.1 packages so they increase that shm value for installs
especially new installs from tasksel. Otherwise those won't go smoothly.
I had cleared all of postgresql from the machine using --purge with remove
in aptitude and this error continued on a subsequent install attempt with
tasksel.



----------------------------------------------------------------
Microsoft: It never looses its suction.

Jude
<jdashiel-at-shellworld-dot-net>
<http://www.shellworld.net/~jdashiel/nj.html>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: alpine.BSF.2.01.1207012300030.40878@freire1.furyyj beyq.arg">http://lists.debian.org/alpine.BSF.2.01.1207012300030.40878@freire1.furyyj beyq.arg

new kernel breaks postgresql on postgresql upgrade
 

On Sun, Jul 01, 2012 at 11:05:29PM -0400, Jude DaShiell wrote:
> I was fortunate in that I hadn't put any data into that database system
> yet. The 40,000,000 value for shm is higher than the 34 million and

That 40000000 was just some arbitrary value I threw in, I don't know
what it should be.

> change value that postgresql was using before and that would explain why
> this failure happened. However, it will be a good idea to fix the
> postgresql 9.1 packages so they increase that shm value for installs

I'm fairly sure that a package shouldn't go around changing system
values which is the responsibility of some other package.

> especially new installs from tasksel. Otherwise those won't go smoothly.
> I had cleared all of postgresql from the machine using --purge with remove
> in aptitude and this error continued on a subsequent install attempt with
> tasksel.

Could you report a bug please, against the postgresql 9.1 package using reportbug?

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120702032257.GB17569@tal