Re: [GENERAL] Problems with new data location

2001-05-30 Thread Tom Lane
"Karen Ellrick" <[EMAIL PROTECTED]> writes: > Yup, the key is that both those methods copy (rather than move) the > directory. If you copy, you can use restart (I assume - I didn't try it). Just for the benefit of the archives: copying the directory tree while the postmaster is live is exactly w

RE: [GENERAL] Problems with new data location

2001-05-29 Thread Karen Ellrick
Tom Lane wrote: > But ... um ... did you restart the postmaster with the new path argument? > Or only change the script? Well, now I can't remember the exact sequence I used originally - I probably tried to restart only after all the changes had taken place. I do remember getting the error "can't

Re: [GENERAL] Problems with new data location

2001-05-29 Thread Tom Lane
"Karen Ellrick" <[EMAIL PROTECTED]> writes: > ... Then I tried creating /var/pgdata fresh and doing initdb -D > /var/pgdata, and that was okay until I tried to create the database again, > when it said a database of that name already existed. Yes, I have changed > my startup script to reflect the

[GENERAL] Problems with new data location

2001-05-29 Thread Karen Ellrick
Right after a new installation (7.1.1) and building my first table with the data directory being the normal /usr/local/pgsql/data, I decided I wanted to put my data directory on a different partition, for space reasons (room for database growth) - I chose /var/pgdata. At first I tried just copying