Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

2012/10/8 Ralf Schuchardt > > > Using sysctl to set the shm* values has consistently worked for us in the > last years ... > > probably i missed that point because my last install of postgres was on ubuntu... > > Mountain Lion comes with it's own version of PostgreSQL. The included psql > comma

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

Am 08.10.2012 um 02:08 schrieb Yvon Thoraval : > 2012/10/7 Scott Marlowe > 'd have posted more, but > > 1: I know just enough about MacOS to be dangerous and > 2: MacOS is known for changing how shared memory works from one minor > patch to another so.. > 3: Any page on making work will be depe

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

2012/10/7 Scott Marlowe > 'd have posted more, but > > 1: I know just enough about MacOS to be dangerous and > 2: MacOS is known for changing how shared memory works from one minor > patch to another so.. > 3: Any page on making work will be dependent on the exact MacOS > version you are running.

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

On Sun, Oct 7, 2012 at 1:59 PM, Yvon Thoraval wrote: > > > 2012/10/7 Scott Marlowe >> >> http://www.postgresql.org/docs/9.2/static/kernel-resources.html > > OK, fine thanks to both. > > I've found a page dealing with that prob : > Fixing the postgresql initdb fatal shared memory error on Leopard

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

2012/10/7 Scott Marlowe > http://www.postgresql.org/docs/9.2/static/kernel-resources.html OK, fine thanks to both. I've found a page dealing with that prob : Fixing the postgresql initdb fatal shared memory error on Leopard

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

On Sun, Oct 7, 2012 at 7:30 AM, Yvon Thoraval wrote: > > I've just installed PostgreSQL, using brew, on Mac OS Mountain Lion. > The server doesn't start and the log file shows : > > $ cat /usr/local/var/postgres/server.log > FATAL: could not create shared memory segment: Cannot allocate memory >

Re: [GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

On 10/07/12 6:30 AM, Yvon Thoraval wrote: What is the workaround ? exactly what the error says to do, increase SHMMAX and SHMMAL in your kernel configuration. on differnet unix-like systems you do this differently (/etc/system on vintage Solaris, /etc/sysctl.conf on most Linux distros, et

[GENERAL] [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory

I've just installed PostgreSQL, using brew, on Mac OS Mountain Lion. The server doesn't start and the log file shows : $ cat /usr/local/var/postgres/server.log FATAL: could not create shared memory segment: Cannot allocate memory DETAIL: Failed system call was shmget(key=5432002, size=3809280, 0

[GENERAL] Mac OS X Lion how to connect to remote server ?

I've installed PostgreSQL using one click installer on Mac OS X Lion. I'd like to query this server from the net. How to allow specific IPV6 addresses to connect to the databases 'addressbook', 'cli', 'landp' and 'landp_public' ? I've tested a simple solution using ssh port forwarding : $ ssh -

Re: [GENERAL] Mac OS X 10.6 - libpq.dylib vs. libpq.a and PQisthreadsafe()

On 2011-10-17, at 4:23 PM, Tom Lane wrote: > > Hm, is there a libpq dylib in /usr/lib? If so, maybe it's capturing the > reference? "otool -L main" would be informative about which dylib is > actually getting called, I think. If it's not what you expected, the > lack of a -L switch in your link

Re: [GENERAL] Mac OS X 10.6 - libpq.dylib vs. libpq.a and PQisthreadsafe()

David McKeone writes: > I've been getting acquainted with the C interface for libpq and have run into > an issue with trying to link to the dynamic libpq while still getting thread > safety. I have tried the following by compiling the 9.1 source with the > --enable-thread-safety flag and I've

[GENERAL] Mac OS X 10.6 - libpq.dylib vs. libpq.a and PQisthreadsafe()

Hello, I've been getting acquainted with the C interface for libpq and have run into an issue with trying to link to the dynamic libpq while still getting thread safety. I have tried the following by compiling the 9.1 source with the --enable-thread-safety flag and I've tried the libpq librari

Re: [GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

On Sep 24, 2011, at 4:21 PM, Guillaume Lelarge wrote: > On Sat, 2011-09-24 at 14:43 -0500, Neil Tiffin wrote: >> On Sep 24, 2011, at 1:31 PM, Joe Conway wrote: >> >>> On 09/23/2011 02:33 PM, Neil Tiffin wrote: I have shared_buffers in the config file set for 32 MB and pgAdmin reports a

Re: [GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

On Sun, 2011-09-25 at 12:13 -0500, Neil Tiffin wrote: > On Sep 24, 2011, at 4:21 PM, Guillaume Lelarge wrote: > > > On Sat, 2011-09-24 at 14:43 -0500, Neil Tiffin wrote: > >> On Sep 24, 2011, at 1:31 PM, Joe Conway wrote: > >> > >>> On 09/23/2011 02:33 PM, Neil Tiffin wrote: > I have shared_

Re: [GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

On Sat, 2011-09-24 at 14:43 -0500, Neil Tiffin wrote: > On Sep 24, 2011, at 1:31 PM, Joe Conway wrote: > > > On 09/23/2011 02:33 PM, Neil Tiffin wrote: > >> I have shared_buffers in the config file set for 32 MB and pgAdmin > >> reports a value of 32 MB, but pgAdmin also says the current value is

Re: [GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

On Sep 24, 2011, at 1:31 PM, Joe Conway wrote: > On 09/23/2011 02:33 PM, Neil Tiffin wrote: >> I have shared_buffers in the config file set for 32 MB and pgAdmin >> reports a value of 32 MB, but pgAdmin also says the current value is >> 4096. Can anyone point me to any docs about why the current

Re: [GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

On 09/23/2011 02:33 PM, Neil Tiffin wrote: > I have shared_buffers in the config file set for 32 MB and pgAdmin > reports a value of 32 MB, but pgAdmin also says the current value is > 4096. Can anyone point me to any docs about why the current value > may be different than the config value? Temp

[GENERAL] Mac OS X shared_buffers not same as postgresql.conf file

Hello all, I am hoping someone can help me with 9.0.4 server on 8GB Mac w/Snow Leopard and shared_buffers configuration setting. I have shared_buffers in the config file set for 32 MB and pgAdmin reports a value of 32 MB, but pgAdmin also says the current value is 4096. Can anyone point me

Re: [GENERAL] Mac OS X

I tried to install postgres onto my macbook via 'fink' and don't like it all that much. I decided to install from source, it's a fallback to my slackware days. But fink already created a user postgres and I can't seem to find anything to change it's configuration settings for shell, home

Re: [GENERAL] Mac OS X

On 7/12/07, Tom Allison <[EMAIL PROTECTED]> wrote: I tried to install postgres onto my macbook via 'fink' and don't like it all that much. I decided to install from source, it's a fallback to my slackware days. Try MacPorts (http://www.macports.org/), a modern BSD-style ports system for OS X. T

Re: [GENERAL] Mac OS X

> I tried to install postgres onto my macbook via 'fink' and don't like > it all that much. > I decided to install from source, it's a fallback to my slackware days. > > But fink already created a user postgres and I can't seem to find > anything to change it's configuration settings for shell, h

[GENERAL] Mac OS X

I tried to install postgres onto my macbook via 'fink' and don't like it all that much. I decided to install from source, it's a fallback to my slackware days. But fink already created a user postgres and I can't seem to find anything to change it's configuration settings for shell, home di

Re: [GENERAL] Mac OS X

On Nov 9, 2006, at 9:10 AM, Nathan Leon Pace, MD, MStat wrote: I run an older version of psql (7.2.4) on a Linux machine. I wish to migrate psql to an Intel Mac running OS x 10.4.8. The supported platforms table in postgresql-8.1-US.pdf (page 259) lists Mac OS X with a PPC cpu as being supp

Re: [GENERAL] Mac OS X

On Thu, 2006-11-09 at 10:10 -0700, Nathan Leon Pace, MD, MStat wrote: > I run an older version of psql (7.2.4) on a Linux machine. > > > I wish to migrate psql to an Intel Mac running OS x 10.4.8. > > > The supported platforms table in postgresql-8.1-US.pdf (page 259) > lists Mac OS X with a PP

[GENERAL] Mac OS X

I run an older version of psql (7.2.4) on a Linux machine.I wish to migrate psql to an Intel Mac running OS x 10.4.8.The supported platforms table in postgresql-8.1-US.pdf (page 259) lists Mac OS X with a PPC cpu as being supported, but not Mac OS X with a Intel cpu.Can psql run on an Intel Mac?Hav

Re: [GENERAL] mac os x compile failure

On Jan 24, 2006, at 9:21 , Michael Glaesemann wrote: On Jan 22, 2006, at 3:10 , Tom Lane wrote: That's odd --- AFAIR I've never had trouble building bison on my OS X laptop. What happens when you try? I neglected to take any notes. I remember it was complaining about "muscle" something-

Re: [GENERAL] mac os x compile failure

On Jan 22, 2006, at 3:10 , Tom Lane wrote: That's odd --- AFAIR I've never had trouble building bison on my OS X laptop. What happens when you try? I neglected to take any notes. I remember it was complaining about "muscle" something-or-other during make. One workaround would be to check

Re: [GENERAL] mac os x compile failure

Michael Glaesemann <[EMAIL PROTECTED]> writes: > Unfortunately I don't have a recent-enough version of bison on the > 10.2 machine and can't get bison-1.875 or bison-2.1 to compile so I > can't install from CVS. I'll definitely check when 8.1.3 is released. That's odd --- AFAIR I've never had

Re: [GENERAL] mac os x compile failure

On Jan 18, 2006, at 9:17 , Michael Glaesemann wrote: On Jan 18, 2006, at 4:56 , Tom Lane wrote: I'll try to see that this gets fixed for PG 8.1.3, but in the short run you might be best off to update your OS X installation, or revert to PG 8.0.* which doesn't try to use FULLFSYNC at all.

Re: [GENERAL] mac os x compile failure

Thanks for the help, Tom, and others who made suggestions. I compiled and installed 8.0.6 with no problems on OS X 10.2.8 My little old imac's a happy postgres host now. Neil --- Tom Lane <[EMAIL PROTECTED]> wrote: > Neil Brandt <[EMAIL PROTECTED]> writes: > > fd.c: In function `pg_fsync_write

Re: [GENERAL] mac os x compile failure

On Jan 18, 2006, at 4:56 , Tom Lane wrote: I'll try to see that this gets fixed for PG 8.1.3, but in the short run you might be best off to update your OS X installation, or revert to PG 8.0.* which doesn't try to use FULLFSYNC at all. Thanks for working on this, Tom. I've got a Mac OS X 10

Re: [GENERAL] mac os x compile failure

Neil Brandt <[EMAIL PROTECTED]> writes: > fd.c: In function `pg_fsync_writethrough': > fd.c:271: `F_FULLFSYNC' undeclared (first use in this function) > fd.c:271: (Each undeclared identifier is reported only once > fd.c:271: for each function it appears in.) Hmm. This is our bug: the code mistake

Re: [GENERAL] mac os x compile failure

Neil Brandt wrote: I'm trying to compile postgres 8.1.2 on OS X 10.2.8. Unfortunately I'm not much of a compile-your-own guy, and I've hit a compile error that's beyond my improvisation abilities, and gets no google hits either. Make your life easy. Use Darwin ports: http://darwinports.op

[GENERAL] mac os x compile failure

I'm trying to compile postgres 8.1.2 on OS X 10.2.8. Unfortunately I'm not much of a compile-your-own guy, and I've hit a compile error that's beyond my improvisation abilities, and gets no google hits either. I realize this also an OS X expert thing: I'm also seeking help on one of the apple.

[GENERAL] Mac OS X 10.3 and SYSV shared memory settings

Because I was just burned by this, I'd like to remind OS X users that OS 10.3 (Panther) may be a less desirable platform than 10.2 for running PostgreSQL and other applications that benefit from customizing SYSV shared memory settings. The problem is that in 10.3, there unbelievably seems to be