Hey there;
As Tom notes before maybe you're not using the right postgres. Solaris 10
comes with a postgres, but on SPARC it's 32 bit compiled (I can't speak to
x86 Solaris though).
Assuming that's not the problem, you can be 100% sure if your Postgres
binary is actually 64 bit by using the file
On Mon, Jul 14, 2008 at 9:13 PM, Greg Smith <[EMAIL PROTECTED]> wrote:
> On Fri, 11 Jul 2008, Jeffrey Baker wrote:
>
>> Their firmware is, frankly, garbage. In more than one instance we
>> have had the card panic when a disk fails, which is obviously counter
>> to the entire purpose of a RAID. We
On Tue, 15 Jul 2008, Jeffrey Baker wrote:
But most recently in my memory we had an Areca HBA which, when one of
its WD RE-2 disks failed, completely stopped responding to both the
command line and the web management interface.
What operating system/kernel version are you using on these system
On Tue, Jul 15, 2008 at 8:17 AM, Greg Smith <[EMAIL PROTECTED]> wrote:
> On Tue, 15 Jul 2008, Jeffrey Baker wrote:
>
>> But most recently in my memory we had an Areca HBA which, when one of its
>> WD RE-2 disks failed, completely stopped responding to both the command line
>> and the web management
"Uwe Bartels" <[EMAIL PROTECTED]> writes:
> When trying to to set shared_buffers greater then 3,5 GB on 32 GB x86
> machine with solaris 10 I running in this error:
> FATAL: requested shared memory size overflows size_t
> The solaris x86 ist 64-bit and the compiled postgres is as well 64-bit.
Eit
Hi,
When trying to to set shared_buffers greater then 3,5 GB on 32 GB x86
machine with solaris 10 I running in this error:
FATAL: requested shared memory size overflows size_t
The solaris x86 ist 64-bit and the compiled postgres is as well 64-bit.
Postgresql 8.2.5.
max-shm ist allowed to 8GB.
pr