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 installer on Lion

Alternatively you can get the 'server' package from app store, it has postgresql already in it :) (9.0) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] mac installer on Lion

Wondering in their is an ETA on a dmg installer for the mac that does not fail on Lion? Best, -Travis

Re: [GENERAL] Mac OSX 10.6 libpq.5.dylib

On Feb 19, 2011, at 4:09 AM, PANAGIOTIS GERMANIS wrote: > Dyld Error Message: > Library not loaded: libpq.5.dylib > Referenced from: > /Volumes/Documents/Projects/Mac_Software/iMacProjects/macReport/build/Release/macReport.app/Contents/MacOS/macReport > Reason: image not found There are tw

[GENERAL] Mac OSX 10.6 libpq.5.dylib

My application builds successfully in Xcode and runs without problems in my mac (running snow leopard 10.6.6) because I have properly installed the postgres 9.0 software. But when I am trying to run my application in an other mac (that hasn't the postgres installed) I get the following error: D

[GENERAL] Mac OSX 10.6 libpq.5.dylib

My application builds successfully in Xcode and runs without problems in my mac (running snow leopard 10.6.6) because I have properly installed the postgres 9.0 software. But when I am trying to run my application in an other mac (that hasn't the postgres installed) I get the following error: D

Re: [GENERAL] Mac OS Roman import?

On Oct 19, 2009, at 4:39 PM, Scott Ribe wrote: On OS X it definitely does; on other platforms it may not since supported encodings are platform-dependent. The Centos version knows about it as well; thanks, that's the perfect solution. -- -- Christophe Pettus x...@thebuild.com -- Sen

Re: [GENERAL] Mac OS Roman import?

> Maybe iconv knows about it? On OS X it definitely does; on other platforms it may not since supported encodings are platform-dependent. -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice -- Sent via pgsql-general mailing list (pgsql-general@postgresql

Re: [GENERAL] Mac OS Roman import?

Christophe Pettus writes: > I find myself needing to regularly import data encoded as Mac OS Roman > (yes, it is coming from an Macintosh OS 9 system) into a UTF-8 > PostgreSQL database. Any advice on how to do so, since Mac OS Roman > is (reasonably enough) not one of PG's standard charact

Re: [GENERAL] Mac OS Roman import?

> I find myself needing to regularly import data encoded as Mac OS Roman > (yes, it is coming from an Macintosh OS 9 system) into a UTF-8 > PostgreSQL database. Any advice on how to do so, since Mac OS Roman > is (reasonably enough) not one of PG's standard character encodings? Use iconv; it's a

Re: [GENERAL] Mac OS Roman import?

On Mon, Oct 19, 2009 at 02:54:38PM -0700, Christophe Pettus wrote: > I find myself needing to regularly import data encoded as Mac OS Roman > (yes, it is coming from an Macintosh OS 9 system) into a UTF-8 > PostgreSQL database. How tightly integrated into PG do you want it? You can define cus

[GENERAL] Mac OS Roman import?

Greetings, I find myself needing to regularly import data encoded as Mac OS Roman (yes, it is coming from an Macintosh OS 9 system) into a UTF-8 PostgreSQL database. Any advice on how to do so, since Mac OS Roman is (reasonably enough) not one of PG's standard character encodings? Thanks

Re: [GENERAL] Mac ordering with locales

On Thu, Feb 21, 2008 at 12:01 PM, Tom Lane wrote: > Pascal Cohen writes: >> The fact is that works on Linux and win but under Mac I always get the >> ordering with 'default' C locale (I displayed all the lc_* and all are >> right set) > > Yeah, this has been complained of before, eg here > http:/

Re: [GENERAL] mac install question

On Thu, Jul 24, 2008 at 6:51 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > Dave Page <[EMAIL PROTECTED]> writes: >>> What are you using it for that you need it to be present at install >>> time? > >> The linker hardcodes library paths into exes and libs. We examine >> these paths at install time using

Re: [GENERAL] mac install question

On Thu, Jul 24, 2008 at 3:57 PM, Shane Ambler <[EMAIL PROTECTED]> wrote: > Shane Ambler wrote: >> >> [EMAIL PROTECTED] wrote: >> >>> Is the otool program on your system anywhere? Afaik, it should be on >>> any Mac, but maybe it's part of xcode (i hope not- can anyone >>> confirm?) >> >> I have a fe

Re: [GENERAL] mac install question

On Thu, Jul 24, 2008 at 12:55 PM, John DeSoi <[EMAIL PROTECTED]> wrote: > > On Jul 24, 2008, at 1:51 AM, Tom Lane wrote: > >> Relative paths sound like the best solution to me, assuming they work. > > Relative paths work fine. I use this all the time for distributing psql. It > looks something like

Re: [GENERAL] mac install question

Shane Ambler wrote: [EMAIL PROTECTED] wrote: Is the otool program on your system anywhere? Afaik, it should be on any Mac, but maybe it's part of xcode (i hope not- can anyone confirm?) I have a few installs here. now that I think about it - it may be a dev tools only thing. otool is incl

Re: [GENERAL] mac install question

On Jul 24, 2008, at 1:51 AM, Tom Lane wrote: Relative paths sound like the best solution to me, assuming they work. Relative paths work fine. I use this all the time for distributing psql. It looks something like this: install_name_tool -change /path/to/postgresql/lib/libpq.dylib @execu

Re: [GENERAL] mac install question

Dave Page <[EMAIL PROTECTED]> writes: >> What are you using it for that you need it to be present at install >> time? > The linker hardcodes library paths into exes and libs. We examine > these paths at install time using otool and rewrite them from the > staging paths on the build machine to

Re: [GENERAL] mac install question

[EMAIL PROTECTED] wrote: Is the otool program on your system anywhere? Afaik, it should be on any Mac, but maybe it's part of xcode (i hope not- can anyone confirm?) I have a few installs here. otool is included inside /Developer/usr/bin my working 10.4 that the dev tools is installed on also

Re: [GENERAL] mac install question

Dave Page wrote: The linker hardcodes library paths into exes and libs. We examine these paths at install time using otool and rewrite them from the staging paths on the build machine to whatever directory the user chose to install to using install_name_tool(1). Yep, the mac linker seems to

Re: [GENERAL] mac install question

On 23 Jul 2008, at 21:47, Tom Lane <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] writes: Thanks for the log. It shows that the otool utility couldn't be found (which should be a fatal error but that's another issue. Is the otool program on your system anywhere? Afaik, it should be on any Mac

Re: [GENERAL] mac install question

[EMAIL PROTECTED] writes: > Thanks for the log. It shows that the otool utility couldn't be found > (which should be a fatal error but that's another issue. > Is the otool program on your system anywhere? Afaik, it should be on > any Mac, but maybe it's part of xcode (i hope not- can anyone > conf

Re: [GENERAL] mac install question

ATH=/Library/PostgreSQL/8.3/lib:$DYLD_LIBRARY_PATH > > > > and running the command again. > > > > -- > > Scott Mead > > Sr. Systems Engineer > > EnterpriseDB > >> Date: Wed, 23 Jul 2008 20:50:13 +0100 >> From: [EMAIL PROTECTED] >> T

Re: [GENERAL] mac install question

it's a command line utility. On 7/23/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Frankly i have no idea what otool is? > >> Date: Wed, 23 Jul 2008 20:45:23 +0100 >> From: [EMAIL PROTECTED] >> To: [EMAIL PROTECTED] >> Subject: Re: [GENERA

Re: [GENERAL] mac install question

>> Date: Wed, 23 Jul 2008 20:01:07 +0100 >> From: [EMAIL PROTECTED] >> To: [EMAIL PROTECTED] >> Subject: Re: [GENERAL] mac install question >> CC: [EMAIL PROTECTED]; pgsql-general@postgresql.org >> >> He does, though he's currently on vacation, bei

Re: [GENERAL] mac install question

On Jul 23, 2008, at 2:19 PM, [EMAIL PROTECTED] wrote: > Date: Wed, 23 Jul 2008 14:12:45 -0400 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [GENERAL] mac install question > CC: pgsql-general@postgresql.org > > On Wed, Jul 23, 2008 at 1:58 PM, [EMAIL

Re: [GENERAL] mac install question

He does, though he's currently on vacation, being forced to top-post in the gmail mobile interface :-p Can the OP send me (privately) the bitrock_installer log from /tmp please? Thanks, Dave On 7/23/08, Douglas McNaught <[EMAIL PROTECTED]> wrote: > On Wed, Jul 23, 2008 at 2:19 PM, [EMAIL PROTECTE

Re: [GENERAL] mac install question

On Wed, Jul 23, 2008 at 2:19 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Well I got it from a link on postgresql.org. Of course it does say that it > is a beta installer. > http://www.postgresql.org/download/macosx Well, hopefully the maintainer reads this mailing list then. :) -Doug -

Re: [GENERAL] mac install question

> Date: Wed, 23 Jul 2008 14:12:45 -0400 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [GENERAL] mac install question > CC: pgsql-general@postgresql.org > > On Wed, Jul 23, 2008 at 1:58 PM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > &

Re: [GENERAL] mac install question

On Wed, Jul 23, 2008 at 1:58 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Please excuse my lack of mac knowledge. I installed postgresql 8.3 using the > mac os x 1 click installer onto my brand new powerbook. The install appeared > to go very smooth. If I go to Postgresql under Applica

[GENERAL] mac install question

Please excuse my lack of mac knowledge. I installed postgresql 8.3 using the mac os x 1 click installer onto my brand new powerbook. The install appeared to go very smooth. If I go to Postgresql under Applications it appears as if I can start and stop postgres and open pgadmin. I even creat

Re: [GENERAL] mac ports question

Stephan Szabo wrote: On Sat, 5 Apr 2008, Tom Allison wrote: If it doesn't remove the 8.2 then I guess I can migrate it. But that requires that I still need to get 8.2 running. Right now it complains that it can't find a listening socket at /tmp/... (localhost mode). And I can't find the conf

Re: [GENERAL] mac ports question

On Sat, 5 Apr 2008, Tom Allison wrote: > If it doesn't remove the 8.2 then I guess I can migrate it. > But that requires that I still need to get 8.2 running. > > > Right now it complains that it can't find a listening socket at /tmp/... > (localhost mode). And I can't find the configuration file

Re: [GENERAL] mac ports question

If it doesn't remove the 8.2 then I guess I can migrate it. But that requires that I still need to get 8.2 running. Right now it complains that it can't find a listening socket at /tmp/... (localhost mode). And I can't find the configuration files in this set-up. I do have this running: /opt

Re: [GENERAL] mac ports question

On Sat, 5 Apr 2008, Tom Allison wrote: > I ran into a problem today where somewhere my port of postgresql82 just > stopped working. I'm largely an idiot on Mac because I use is as a > workstation/development box and do most of the real system related work > on my debian boxes. > > But I don't kno

[GENERAL] mac ports question

I ran into a problem today where somewhere my port of postgresql82 just stopped working. I'm largely an idiot on Mac because I use is as a workstation/development box and do most of the real system related work on my debian boxes. But I don't know how to get the port working again. Then I sa

Re: [GENERAL] Mac ordering with locales

On Feb 22, 2008, at 10:16 AM, Martijn van Oosterhout wrote: On Thu, Feb 21, 2008 at 11:14:58AM -0800, Jeff Davis wrote: I have looked for a standard related to the locale behavior and I was surprised that I couldn't find one. Is a given locale, e.g. en_US, supposed to have identical behavior o

Re: [GENERAL] Mac ordering with locales

On Thu, Feb 21, 2008 at 11:14:58AM -0800, Jeff Davis wrote: > I have looked for a standard related to the locale behavior and I was > surprised that I couldn't find one. Is a given locale, e.g. en_US, > supposed to have identical behavior on any platform for which it's > available? > > If there is

Re: [GENERAL] Mac ordering with locales

On Thu, 2008-02-21 at 12:01 -0500, Tom Lane wrote: > Pascal Cohen <[EMAIL PROTECTED]> writes: > > The fact is that works on Linux and win but under Mac I always get the > > ordering with 'default' C locale (I displayed all the lc_* and all are > > right set) > > Yeah, this has been complained of

Re: [GENERAL] Mac ordering with locales

"A.M." <[EMAIL PROTECTED]> writes: > On Feb 21, 2008, at 12:01 PM, Tom Lane wrote: >> It seems to be a deficiency in Apple's locale support. The second >> message is interesting since it indicates that "smart" sorting is >> available somewhere/somehow under OS X, but nobody here knows how >> to ge

Re: [GENERAL] Mac ordering with locales

On Feb 21, 2008, at 12:01 PM, Tom Lane wrote: Pascal Cohen <[EMAIL PROTECTED]> writes: The fact is that works on Linux and win but under Mac I always get the ordering with 'default' C locale (I displayed all the lc_* and all are right set) Yeah, this has been complained of before, eg her

Re: [GENERAL] Mac ordering with locales

Pascal Cohen <[EMAIL PROTECTED]> writes: > The fact is that works on Linux and win but under Mac I always get the > ordering with 'default' C locale (I displayed all the lc_* and all are > right set) Yeah, this has been complained of before, eg here http://archives.postgresql.org/pgsql-general/2

[GENERAL] Mac ordering with locales

Hello We are using different OS (Mac, win (with a small w!) and Linux). We had some problems when doing some ordering on names. I found that it seemed to be related on locale, While on Linux it used default locales (en_US.UTF-8 or something like that), I had a nice behavior). I learned to check

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 Problem with Tunneling...

Jerry LeVan wrote: > Hi, > On my linux box I can issue the command > > ssh -L :macjerry:5432 -l jerry macjerry > > This will create a "tunnel" to connect to my > mac named "macjerrry". > > I can connect to databases on macjerry via psql > by specifying port on my linux box and other

Re: [GENERAL] Mac Problem with Tunneling...

On Sat, 13 May 2006, Jerry LeVan wrote: channel 3: open failed: administratively prohibited: open failed This is the standard error you'll see when /etc/ssh/sshd_config (or local equivalent) has AllowTcpForwarding no. Kris Jurka ---(end of broadcast)-

Re: [GENERAL] Mac Problem with Tunneling...

On May 13, 2006, at 6:18 PM, Tom Lane wrote: Jerry LeVan <[EMAIL PROTECTED]> writes: How ever if I turn it around, and on the mac issue the command ssh -L :linuxbox:5432 -l jerry linuxbox Then I am not able to connect to the linux box via psql or any Gui front ends. [ tries it ... ]

Re: [GENERAL] Mac Problem with Tunneling...

Jerry LeVan <[EMAIL PROTECTED]> writes: > How ever if I turn it around, and on the mac issue > the command > ssh -L :linuxbox:5432 -l jerry linuxbox > Then I am not able to connect to the linux box > via psql or any Gui front ends. [ tries it ... ] Worksforme, using the stock ssh in OS X

[GENERAL] Mac Problem with Tunneling...

Hi, On my linux box I can issue the command ssh -L :macjerry:5432 -l jerry macjerry This will create a "tunnel" to connect to my mac named "macjerrry". I can connect to databases on macjerry via psql by specifying port on my linux box and other postgresql front ends. How ever if I

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

[GENERAL] Mac

To many thanks for the helpfull info. My brief is:: (1) fix FileMaker for the forseable future (2) Look at alternatives. At the moment nothing beyond that is determined. Apple moving to OSX may change availability of some clients So I'm looking at all suggestions but not rushing. Furhter sug

Re: [GENERAL] Mac Connectivity

-Original Message- From: Andrew Gibson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Wednesday, July 29, 1998 1:59 PM Subject: [GENERAL] Mac Connectivity >Hi, > >Has anyone achieved Macintosh connectivity to PostgreSQL? Yes, but with the p

Re: [GENERAL] Mac Connectivity

Andrew Gibson wrote: > > Hi, > > Has anyone achieved Macintosh connectivity to PostgreSQL? > > If so, any details would be appreciated i.e. which ODBC driver > > Thanks, > > - > ANDREW GIBSON (Director - Information Services) > Cannon Hi

Re: [GENERAL] Mac Connectivity

> At 2:58 +0300 on 29/7/98, Andrew Gibson wrote: > > > Has anyone achieved Macintosh connectivity to PostgreSQL? > > > > If so, any details would be appreciated i.e. which ODBC driver > > Not by ODBC, but generally you can do it with Java or TCL. I had a bit of a > problem with the TCL interface,

Re: [GENERAL] Mac Connectivity

At 2:58 +0300 on 29/7/98, Andrew Gibson wrote: > Has anyone achieved Macintosh connectivity to PostgreSQL? > > If so, any details would be appreciated i.e. which ODBC driver Not by ODBC, but generally you can do it with Java or TCL. I had a bit of a problem with the TCL interface, but my guess

[GENERAL] Mac Connectivity

Hi, Has anyone achieved Macintosh connectivity to PostgreSQL? If so, any details would be appreciated i.e. which ODBC driver Thanks, - ANDREW GIBSON (Director - Information Services) Cannon Hill Anglican College http://www.chac.qld.edu.a

[GENERAL] Mac Connectivity

Hi, Has anyone achieved Macintosh connectivity to PostgreSQL? If so, any details would be appreciated i.e. which ODBC driver Thanks, - ANDREW GIBSON (Director - Information Services) Cannon Hill Anglican College http://www.chac.qld.edu.a