Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ox6Am-0007ed-Np for pgsql-admin@arkaria.postgresql.org; Mon, 21 Nov 2022 12:45:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ox6Ak-0007uu-Tp for pgsql-admin@arkaria.postgresql.org; Mon, 21 Nov 2022 12:45:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ox6Ak-0007ul-Gi for pgsql-admin@lists.postgresql.org; Mon, 21 Nov 2022 12:45:14 +0000 Received: from mx3.stadt-zuerich.ch ([194.56.33.12]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ox6Ai-0004pJ-0O for pgsql-admin@lists.postgresql.org; Mon, 21 Nov 2022 12:45:14 +0000 IronPort-SDR: w9OcZU887obvEbTp/CvDDARdr7YEpITCdvsxdi2GAkWBdldFj08/HInsWPXx6c+jceBecbDSIx BMjl2uZXInk7SPEdYIgG91OQC6qyOSjKi3LqVepwBcJJk+3NlL+dmKCuw4eHup98sV/7GVcypS pozQ5QQ3eVjD54S46fJchit3Cy6xMPbYeNJJGGpErrYhur/hiISpHssfRLG06KuzLznnaFkmb8 CZOxRayOB5DmVpyGHFmSv4/SquiiL6LvjLszKY0xeCkhqXwAPYq4Ytrqjk9d+8POXVO9OORGpi eEw= X-IronPort-AV: E=Sophos;i="5.96,181,1665439200"; d="scan'208,217";a="125795419" Received: from unknown (HELO SZHM27372.global.szh.loc) ([10.7.50.60]) by mx3.prm.szh.zone with ESMTP/TLS/AES256-GCM-SHA384; 21 Nov 2022 13:45:10 +0100 Received: from SZHM27370.global.szh.loc (10.7.50.50) by SZHM27372.global.szh.loc (10.7.50.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.18; Mon, 21 Nov 2022 13:45:10 +0100 Received: from SZHM27370.global.szh.loc ([fe80::2839:247b:c8d4:9198]) by SZHM27370.global.szh.loc ([fe80::2839:247b:c8d4:9198%10]) with mapi id 15.01.2375.018; Mon, 21 Nov 2022 13:45:10 +0100 From: "Zwettler Markus (OIZ)" To: "pgsql-admin@lists.postgresql.org" Subject: how can one infer the maximum possible restore time from a WAL file(name) in a backup? Thread-Topic: how can one infer the maximum possible restore time from a WAL file(name) in a backup? Thread-Index: Adj9pusSDvidp2HdTzijdwAqs4qfug== Date: Mon, 21 Nov 2022 12:45:10 +0000 Message-ID: <173875f2fb734d46877eecf55ae0682e@zuerich.ch> Accept-Language: de-CH, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.48.250] Content-Type: multipart/alternative; boundary="_000_173875f2fb734d46877eecf55ae0682ezuerichch_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_173875f2fb734d46877eecf55ae0682ezuerichch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, In Oracle there is a view v$archived_log in which for each logfile the time= of the first and last transaction contained in it is indicated. By means o= f this view one can infer from a log file in the backup the maximum possibl= e recovery time. Is there something similar in Postgres? Or in other words, how can one infe= r the maximum possible restore time from a WAL file(name) in a backup? Thanks, Markus --_000_173875f2fb734d46877eecf55ae0682ezuerichch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

In O= racle there is a view v$archived_log in which for each logfile the time of = the first and last transaction contained in it is indicated. By means of th= is view one can infer from a log file in the backup the maximum possible recovery time.

Is t= here something similar in Postgres? Or in other words, how can one infer th= e maximum possible restore time from a WAL file(name) in a backup?

Than= ks, Markus

--_000_173875f2fb734d46877eecf55ae0682ezuerichch_--