On 11/30/2015 09:54 AM, anj patnaik wrote:
1) directory listing:
/opt/nfsDir/postgres/9.4/
/bin
/data
/etc
/pgAdmin3
....
2) The way I am using PG now is that I have specified the directory
above as the location to install it (from graphical installer).
Now, it appears that postgres places files in other directories besides
the one specified in the installer. For instance, there are scripts in
/etc/init.d to start the service.
Answers without context are not answers.
Where is /etc/init.d located, the machine that has the NFS mount or
another machine?
So in answering my own question: it appears PG places files in other
dirs so when I am given a new VM/different physical server with the same
NFS mount I would either need to copy these files over or better yet
un-install the current PG and re-install from scratch.
Why not save yourself a lot of trouble, and if it is not the case
already, set up Postgres on a central server and connect to it from
whatever client you wish.
Thanks,
ap
On Fri, Nov 27, 2015 at 8:30 PM, Adrian Klaver
<adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> wrote:
On 11/27/2015 01:17 PM, anj patnaik wrote:
Hello,
Yes, postgres is currently installed on a nfs mounted file
system. So
when graphical installer runs, there is a form which asks
location for
installation. I specified this path /opt/nfsDir/Postgres where
nfsDir is
a nfs mount. So currently this is where PG 9.4 lives.
What is under /opt/nfsDir/Postgres?
My question is when I am given a brand new VM on a different
physical
server, can I mount that same NFS FS and use the Postgres or do
I need
to re-install PG on new VM?
How are you using Postgres now? Please be specific, more detail is
better then less at this point.
I am not sure if PG writes to any other directories besides the one
where it is installed.
On the issue of logging, I see a lot of log statements because
client
apps do upserts and since I use Tcl I don't have a SQL proc, but
rather
I let it exception and then do an update on the row.
You can Tcl in the database:
http://www.postgresql.org/docs/9.4/interactive/pltcl.html
That will not change things if you let the database throw an
exception there also.
So, you can limit the size of an individual log, but there is no
way to
tell PG to keep the log file short?
if i choose FATAL, I'd lose some log, right?
Thank you!
ap
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
