Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 7F2729F99B4 for ; Fri, 24 Aug 2007 15:48:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 11843-05 for ; Fri, 24 Aug 2007 15:48:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by postgresql.org (Postfix) with ESMTP id E66979F9B1F for ; Fri, 24 Aug 2007 15:48:32 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id u77so2119580pyb for ; Fri, 24 Aug 2007 11:48:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=gtBZIVUdh6gd/oNFRQtJyVE0DmKQtatykkCUe/Z5G5LI7Zgqv1gXLAJctp1Hg6SbIUTeCqZx4TQxnsoRveAkaZM0pXRIx0drzuUogBhaeQPcYQRbTmRxAsD6gyACq3OLMafn9nNaAa7O+lv4WqTjReEfYwKMmwWZGKv+ycwyt+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Hv/bNzDRqzmenjW5m25f6RwhDe05H4RpEYWMtWMfPUdv0KPhnz9HfGPQqnKwykFfQkCVEnLO8xfrrjIZRRyWYP8Ma5m7SDBj//iboBEdT+6plxDtg1aozB/WRGeIUgzvsm/arzZBh7IzWUJ4HzkM8UlPuqjHMEETwZ5eRdwyqaU= Received: by 10.65.214.2 with SMTP id r2mr6134785qbq.1187981308647; Fri, 24 Aug 2007 11:48:28 -0700 (PDT) Received: by 10.65.110.15 with HTTP; Fri, 24 Aug 2007 11:48:28 -0700 (PDT) Message-ID: <8078a1730708241148i58ed7dadyd290efec6e0bfec3@mail.gmail.com> Date: Fri, 24 Aug 2007 11:48:28 -0700 From: "Medi Montaseri" To: "Campbell, Lance" Subject: Re: Installing Postgres Cc: "Tom Lane" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_178335_20803258.1187981308199" References: <10725.1187894512@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/319 X-Sequence-Number: 26650 ------=_Part_178335_20803258.1187981308199 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Just dont get into the habbit of moving db files around like too much....filesystems will spead your files all over the place and your database will slow down.... Medi On 8/23/07, Campbell, Lance wrote: > > Tom, > > > It is nice to know that you can actually move the database by simply > moving the files. That does assume you shut down the database first. > > Thanks, > > Lance Campbell > Project Manager/Software Architect > Web Services at Public Affairs > University of Illinois > 217.333.0382 > http://webservices.uiuc.edu > > > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Thursday, August 23, 2007 1:42 PM > To: Campbell, Lance > Cc: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] Installing Postgres > > "Campbell, Lance" writes: > > The solution, based on emails I have received, is to install > PostgreSQL > > into a subdirectory called "data". I then move the contents of "data" > > back a directory. This way I am able to have the files in the > directory > > I want them in. Even though the directory I wanted them in contains a > > subdirectory. This is how you get around the issue. > > NO, NO, NO, NO, NO. > > You appear to be impervious to several people telling you this is a > bad idea, but I will try one more time to explain why. The reason you > see "lost+found" in that directory is that it is a volume mount point. > Volume mount point directories should *always* be owned by root, for > both reliability and security reasons. The setup you are proposing > would have to have the mount point directory be postgres-owned. > You will live to regret that if you insist on doing it that way > (in fact, I'm astonished your sysadmin agreed to it in the first > place ... he must be pretty new at his job). > > Stick with the extra level of directory. > > > It appears that > > the PostgreSQL data directory contents can be moved. > > Yeah, they can. The argument here is about exactly where you are > proposing to move them to. If it were an ordinary directory it'd be > fine. > > regards, tom lane > > ---------------------------(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 > ------=_Part_178335_20803258.1187981308199 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Just dont get into the habbit of moving db files around like too much....filesystems will spead your files all over the place and your database will slow down....

Medi

On 8/23/07, Campbell, Lance <lance@uiuc.edu> wrote:
Tom,


It is nice to know that you can actually move the database by simply
moving the files.  That does assume you shut down the database first.

Thanks,

Lance Campbell
Project Manager/Software Architect
Web Services at Public Affairs
University of Illinois
217.333.0382
http://webservices.uiuc.edu


-----Original Message-----
From: Tom Lane [mailto: tgl@sss.pgh.pa.us]
Sent: Thursday, August 23, 2007 1:42 PM
To: Campbell, Lance
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Installing Postgres

"Campbell, Lance" <lance@uiuc.edu> writes:
> The solution, based on emails I have received, is to install
PostgreSQL
> into a subdirectory called "data".  I then move the contents of "data"
> back a directory.  This way I am able to have the files in the
directory
> I want them in.  Even though the directory I wanted them in contains a
> subdirectory.  This is how you get around the issue.

NO, NO, NO, NO, NO.

You appear to be impervious to several people telling you this is a
bad idea, but I will try one more time to explain why.  The reason you
see "lost+found" in that directory is that it is a volume mount point.
Volume mount point directories should *always* be owned by root, for
both reliability and security reasons.  The setup you are proposing
would have to have the mount point directory be postgres-owned.
You will live to regret that if you insist on doing it that way
(in fact, I'm astonished your sysadmin agreed to it in the first
place ... he must be pretty new at his job).

Stick with the extra level of directory.

> It appears that
> the PostgreSQL data directory contents can be moved.

Yeah, they can.  The argument here is about exactly where you are
proposing to move them to.  If it were an ordinary directory it'd be
fine.

                        regards, tom lane

---------------------------(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

------=_Part_178335_20803258.1187981308199--