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 4000 was just some arbitrary value I threw in, I don't know
what it should be.
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
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
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.
4 matches
Mail list logo
