[patch] INSTALL doc note (was Re: [BUGS] BUG #1051: Cannot remove groups) - Mailing list pgsql-patches

From jari.aalto@poboxes.com (Jari Aalto)
Subject [patch] INSTALL doc note (was Re: [BUGS] BUG #1051: Cannot remove groups)
Date
Msg-id 8yk64xgz.fsf@blue.sea.net
Whole thread Raw
Responses Re: [patch] INSTALL doc note (was Re: [BUGS] BUG #1051: Cannot remove groups)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches

    "PostgreSQL Bugs List" <pgsql-bugs@postgresql.org> writes:
    > I tried to install all from  fresh with:
    > ...
    > But that dind't affect the groups or users. This was verified by running
    > select from pg_group and pg_users immedately after total recreation.

    Tom Lane:
    Your trace shows no sign of having stopped the postmaster before
    re-initdb'ing or starting it again afterwards.  I think you've got some
    unholy combination of old and new tables inside the postmaster.  It'd be
    a good idea to try again with those steps included.  (I'm not sure just
    how Windows handles deletion of directories that are still in use, but
    on Unix a pg_ctl stop would no longer suffice to get rid of the old
    postmaster, because after the rm -rf you can no longer get to the
    directory in which the old postmaster is running.  You might be best
    advised to reboot.)

Thank you. That did it. May I suggest adding this:


--- INSTALL.old    2004-01-17 13:34:22.000000000 +0200
+++ INSTALL    2004-01-17 13:33:32.000000000 +0200
@@ -15,6 +15,7 @@
   mkdir /usr/local/pgsql/data
   chown postgres /usr/local/pgsql/data
   su - postgres
+  <kill current postmaster. This clears groups and users>
   LC_ALL=C /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
   /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 &
   /usr/local/pgsql/bin/createdb test


pgsql-patches by date:

Previous
From: Pavel Stehule
Date:
Subject: client_encoding in dump file
Next
From: jari.aalto@poboxes.com (Jari Aalto)
Date:
Subject: [patch] 7.4 initdb - drop trailing slash from $PGDATA