Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etCZy-0005Y7-96 for pgsql-performance@arkaria.postgresql.org; Tue, 06 Mar 2018 13:24:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etCZw-0006xN-Uw for pgsql-performance@arkaria.postgresql.org; Tue, 06 Mar 2018 13:24:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etCZw-0006wv-KH for pgsql-performance@lists.postgresql.org; Tue, 06 Mar 2018 13:24:28 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etCZt-0007cn-Tt for pgsql-performance@postgresql.org; Tue, 06 Mar 2018 13:24:27 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 35B345F79C; Tue, 6 Mar 2018 08:24:25 -0500 (EST) Date: Tue, 6 Mar 2018 08:24:25 -0500 From: Stephen Frost To: Rambabu V Cc: pgsql-performance@postgresql.org Subject: Re: need meta data table/command to find query log Message-ID: <20180306132425.GM2416@tamriel.snowman.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qsQaRJFLj5QNDUlH" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --qsQaRJFLj5QNDUlH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, These questions are not appropriate for the 'performance' mailing list but should be either on 'admin' or 'general'. Please use the appropriate list for asking questions in the future. * Rambabu V (ram.wissen@gmail.com) wrote: > Please help us to get the query log details from meta data table/command in > postgresql. aw we are not maintaining log files more than 2 days due to > lack of space. It's entirely unclear what you are asking for here when you say "meta data." Information about tables is stored in the system catalog, particularly the "pg_class" and "pg_attribute" tables, but that's independent from the WAL. To read the WAL files, you can use pg_waldump (or pg_xlogdump on older versions), though that's not 'meta' data. > And also please provide document or sop for database upgrade from 9.3 to > 9.6, as our database size was 4.5 tb and having table spaces as well. as it > was production database system we do-not want to take any risk, please help > us on this as well. You'll likely want to use pg_upgrade to perform such an upgrade: https://www.postgresql.org/docs/10/static/pgupgrade.html Thanks! Stephen --qsQaRJFLj5QNDUlH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJanpaIAAoJEO1sijiDR2RViJ8P/0rVUS/9GJIOA/jTC4CjiP3q axWsh2O73r9FgyAqeOTI6geHrEV+cxezHuw7aqVFvGlW8Mueqr8btH8h9jvv6mTR 1s7WGu7I9oTRAc925mQPYsrg89BKb2rEXEt66HJLZ1QQ6ipKs0AIf85r9nkR8888 Wt9bhrtePB+jEIh7gm6VKkhCZfHP5jXeYs3dxYN+PtGc5Ushi7zRAaIlXdqdNM/J 3ByOL0fSHzz8xS3zFSG5grvxj+RifwIHUNCYUy4tJGy/PqlD88ExDKe4GzqzN3zs nhxUDFT1x0jKPW3qoUbheoTQBHz8okfAOqi20PzhmV3ih0wwNbATy+RsySNe+2Tm B3w44qQmvdENJA3y7FqwyTJwJcSWM6DIkgmuwPd0Gr2TUzgHJO1t9RCd68bMi8Hv pqWSqwkC9fueP1RuZSsTq8tYHPeLr3XUwHraCmWgcoj0UIybS5oO6zi9VsYUHcUf tjZVH5u0/FDQymarRoVdHnrwI+LPabj9NPEq3NI5B8hQyWBnBZVW9uvo16tTH6AV uakOvHaCGf94kLWTEUPJgpcB+4Q4azEkpNB+SgQPKOvsjoYqGUOhjarR9CQ9A73l BCJZtUFWwmiDGgprvFg9YowldASQz6aKn+4j+ex23YDUJ1put6+SUjHlfNuZ89iB whASd2hP7LKM8LusBUMJ =yN3i -----END PGP SIGNATURE----- --qsQaRJFLj5QNDUlH--