John, Hey thanks! I figured out the answer while responding to your suggestion. I had started to write:
Yes, I gave that a shot too, but it didn't work. The problem isn't connecting to the database, but just launching postmaster (with pg_ctl) pointing to that database cluster. Launching fails if the "user launching postmaster" != "the user specified in initdb". It turns out the problem is with launching postmaster via pg_ctl -- in fact, pg_ctl seems to do this user authentication test, but postmaster doesn't. So I found that if I launch postmaster directly, no problem. Nice security :-) Thanks for your suggestions, Jeffrey PS - I still have to do a full blown test where I actually move it to a different machine, but initial tests look solid. on 8/31/06 10:33 AM, John DeSoi at [EMAIL PROTECTED] wrote: > I'm assuming you are running initdb without specifying a user name > (and thus it defaults to the current user). Have you tried running > initdb (and connecting with) a single user name, e.g. postgres? > > I'm not sure if it will work, but maybe worth a shot. > > On Aug 31, 2006, at 12:38 PM, Jeffrey J. Early wrote: > >> Picking up a database cluster and moving it from system to system >> *does* >> seem to work without a hitch as long as the username is the same on >> each >> system. So it seems to me there has to be a fairly simple solution >> to make >> this work. > > > > John DeSoi, Ph.D. > http://pgedit.com/ > Power Tools for PostgreSQL > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
