Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YVV3C-0000G6-UQ for pgsql-admin@arkaria.postgresql.org; Wed, 11 Mar 2015 01:03:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YVV3C-0000Kd-4D for pgsql-admin@arkaria.postgresql.org; Wed, 11 Mar 2015 01:03:06 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YVV39-0000KQ-TW for pgsql-admin@postgresql.org; Wed, 11 Mar 2015 01:03:04 +0000 Received: from mgap1c-mgmt.jacksonnational.com ([12.148.227.38]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YVV34-0002iv-7f for pgsql-admin@postgresql.org; Wed, 11 Mar 2015 01:03:01 +0000 X-IronPort-AV: E=Sophos;i="5.11,378,1422939600"; d="scan'208,217";a="213403902" Received: from vtunpep1c.jacksonnational.com (HELO USPRHCP03C.pgdsresource.local) ([10.12.111.24]) by mgap1c-mgmt.jacksonnational.com with ESMTP; 10 Mar 2015 21:02:55 -0400 Received: from USPRHCP05C.pgdsresource.local (10.11.103.45) by USPRHCP03C.pgdsresource.local (10.11.103.43) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 10 Mar 2015 21:02:54 -0400 Received: from USPRMBP01C.pgdsresource.local ([10.11.103.11]) by USPRHCP05C.pgdsresource.local ([::1]) with mapi id 14.03.0195.001; Tue, 10 Mar 2015 21:02:53 -0400 From: "Rossi, Maria" To: "'pgsql-admin@postgresql.org'" Subject: Relocated Postgres Thread-Topic: Relocated Postgres Thread-Index: AdBblxn2Vqwpm0aZQOOXbpSUXUHeZw== Date: Wed, 11 Mar 2015 01:02:53 +0000 Message-ID: <33A4D5087BF0D44DA69C5EEF666BC1D742507AD2@usprmbp01c> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.8.96.1] X-TM-AS-Product-Ver: SMEX-11.0.0.1251-7.500.1018-21390.003 X-TM-AS-Result: No--18.255100-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Type: multipart/alternative; boundary="_000_33A4D5087BF0D44DA69C5EEF666BC1D742507AD2usprmbp01c_" MIME-Version: 1.0 X-DLP-JNL: Passed X-Pg-Spam-Score: 0.0 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --_000_33A4D5087BF0D44DA69C5EEF666BC1D742507AD2usprmbp01c_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable HI, I relocated an postgres instance. The pg_data, pg_tranlog, pg_hba.conf, et= c were copied to new directories. Then, I updated the postgresql.conf acco= rdingly. Postgres started ok, and I can connect. However when I stopped = it, the following msg appeared at the errorlog: cp: overwrite `/dba/psg/gs07/pg_tranlog/pg_archlog/00000001000000000000004C= '? < 2015-03-10 20:50:38 EDT >LOG: database system is shut down Postgres proceeded to shutdown. 'ls' showed that the file still have the old timestamp, which is the timest= amp when I copied it over: ls -ltr /dba/psg/gs07/pg_tranlog/pg_archlog/00000001000000000000004B -rw------- 1 gs07 dbagroup 16777216 Mar 10 12:07 /dba/psg/gs07/pg_tranlog/p= g_archlog/0000000100 I did not have any transctions, though between the start-up and shutdown. = I would have expected the timestamp of the logfile to have been changed. Looks like it was waiting for a response to 'cp'. I am concerned that if there were any transactions, I would have lost it. Pls advice. Thanks. Maria --_000_33A4D5087BF0D44DA69C5EEF666BC1D742507AD2usprmbp01c_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

HI,

 

I relocated an postgres instance.  The pg_data,= pg_tranlog, pg_hba.conf, etc were copied to new directories.  Then, I= updated the postgresql.conf accordingly.  Postgres started ok, and I = can connect.   However when I stopped it,  the following msg appeared at the errorlog:

 

cp: overwrite `/dba/psg/gs= 07/pg_tranlog/pg_archlog/00000001000000000000004C'? < 2015-03-10 20:50:3= 8 EDT >LOG:  database system is shut down

 

Postgres proceeded to shutdown.  

 

‘ls’ showed that the file still have the= old timestamp, which is the timestamp when I copied it over:

 

ls -ltr /dba/psg/gs07/pg_t= ranlog/pg_archlog/00000001000000000000004B

-rw------- 1 gs07 dbagroup= 16777216 Mar 10 12:07 /dba/psg/gs07/pg_tranlog/pg_archlog/0000000100<= /o:p>

 

I did not have any transctions, though between the s= tart-up and shutdown.  I would have expected the timestamp of the logf= ile to have been changed.

Looks like it was waiting for a response to ‘c= p’.

 

I am concerned that if there were any transactions, = I would have lost it. 

Pls advice.

 

Thanks.

 

Maria

 

--_000_33A4D5087BF0D44DA69C5EEF666BC1D742507AD2usprmbp01c_--