Re: Cygwin-Postgres-IpcMemoryCreate
От | Henshall, Stuart - WCP |
---|---|
Тема | Re: Cygwin-Postgres-IpcMemoryCreate |
Дата | |
Msg-id | E2870D8CE1CCD311BAF50008C71EDE8E01F7484E@MAIL_EXCHANGE обсуждение исходный текст |
Ответ на | Cygwin-Postgres-IpcMemoryCreate (Saravanan Bellan <SBellan@jareva.com>) |
Ответы |
Re: Cygwin-Postgres-IpcMemoryCreate
|
Список | pgsql-cygwin |
> From: Jason Tishler [mailto:jason@tishler.net] > > > On Tue, Apr 16, 2002 at 02:34:08PM -0700, Saravanan Bellan wrote: > > This was initially posted in comp.databases.postgresql.ports.cygwin. > > > > Updates: > > > > If using the rename() instead of link() the following error is not > > experienced anymore. > > > > > 1) FATAL 2: link from > /cygdrive/C/pg/data/pg_xlog/0000000000000004 to > > > /cygdrive/C/pg/data/pg_xlog/0000000000000007 > (initialization of log > > > file 0, segment 7) failed: Permission denied > > Please post your patch for the above, so we know precisely what change > you needed to make to solve your problem. If the patch looks good, > then the next step would be to post it to pgsql-patches for > consideration. > > Note, however, that I have never seen an error message like the above. > What is your system info? > I just saw the above error when trying to upgrade to 7.2.1 from 7.1.3 (as well changing servers) and putting the data in. Here's my error log: DEBUG: recycled transaction log file 0000000000000097 FATAL 1: No pg_hba.conf entry for host 10.20.1.76, user sdb, database dp_test FATAL 1: No pg_hba.conf entry for host 10.20.1.76, user sdb, database dp_test FATAL 2: link from /usr/local/pgsql/data/pg_xlog/0000000000000097 to /usr/local /pgsql/data/pg_xlog/00000000000000A0 (initialization of log file 0, segment 160) failed: Permission denied DEBUG: server process (pid 381) exited with exit code 2 DEBUG: terminating any other active server processes DEBUG: all server processes terminated; reinitializing shared memory and semaph ores IpcMemoryCreate: shmget(key=5432001, size=174891008, 03600) failed: Not enough m emory This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. uname -a: CYGWIN_NT-4.0 DPRINT 1.3.10(0.51/3/2) 2002-02-25 11:14 I686 unknown This is with a self built postgresql-7.2.1 with --enable-debug --enable-depend make check passed all tests. The computer is a Proliant 370 with dual pIII's and 1GB of memory on an NTFS partition. postgres user is currently a member of Administrators, so should have any necessary permissions. I'm wondering if the previous memeory was not freed, therefore putting me above the default memory limit (256MB IIRC). As a side note I've been having trouble getting heap_chunk_in_mb setting in the registry to work. Has any one else managed this with ipc-daemon and postgresql run as services? - Stuart
В списке pgsql-cygwin по дате отправления: