diff options
Diffstat (limited to 'doc/src/sgml/ref')
| -rw-r--r-- | doc/src/sgml/ref/postmaster.sgml | 28 |
1 files changed, 1 insertions, 27 deletions
diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml index beb6c0ee93f..5bf5e4cb92b 100644 --- a/doc/src/sgml/ref/postmaster.sgml +++ b/doc/src/sgml/ref/postmaster.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.16 2000/11/22 01:41:13 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.17 2000/11/28 23:27:54 tgl Exp $ Postgres documentation --> @@ -400,32 +400,6 @@ $ ps -e | grep postmast </para> </listitem> </varlistentry> - - <varlistentry> - <term><computeroutput> -IpcMemoryAttach: shmat() failed: Permission denied - </computeroutput></term> - <listitem> - <para> - A likely explanation is that another user attempted to start a - <application>postmaster</application> - process on the same port which acquired shared resources and then - died. Since Postgres shared memory keys are based on the port number - assigned to the - <application>postmaster</application>, - such conflicts are likely if there is more than one installation on - a single host. If there are no other - <application>postmaster</application> - processes currently running (see above), run - <application>ipcclean</application> - and try again. If other <application>postmaster</application> - images - are running, you will have to find the owners of those processes to - coordinate the assignment of port numbers and/or removal of unused - shared memory segments. - </para> - </listitem> - </varlistentry> </variablelist> </para> </refsect2> |