Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uTHQI-002Kjv-GS for pgsql-admin@arkaria.postgresql.org; Sun, 22 Jun 2025 09:55:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uTHPF-00Byq8-Op for pgsql-admin@arkaria.postgresql.org; Sun, 22 Jun 2025 09:54:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uTHPF-00Byq0-C4 for pgsql-admin@lists.postgresql.org; Sun, 22 Jun 2025 09:54:34 +0000 Received: from cc-smtpout3.netcologne.de ([89.1.8.213]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uTHPD-003SI7-2T for pgsql-admin@lists.postgresql.org; Sun, 22 Jun 2025 09:54:33 +0000 Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout3.netcologne.de (Postfix) with ESMTP id 8F17912127 for ; Sun, 22 Jun 2025 11:54:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1750586070; bh=Ek2i0kLRwdRKqlEGfemsTNQ2O6JIXl8Fx1efvdYcudM=; h=Message-ID:Date:Subject:To:References:From:In-Reply-To:From; b=qK6S5RFijdLFV3Zs0qapqdMnUqLG6/zuqWxJRV3qjEusN+I4vkKAREoEHvVgHaIaF 0nOKzTVFM+1hKwQ+OjZqUXrtEgucNirFwx1mF85VvNwdVfSk70Pu9zbh7ijDeKvYZZ iAfMPsXo1Ylgf4ew12W04koAFtvoVXm+HVHHyXXmWLz+Z3B6KEZTRXJcTI5p5iuQVk 3YE4ElmcRvvhDgIwc0KQY1oQRhbtMFgn6dJA+O1d1/rhwnQ2j6G8uvICYZruZJEx7e GW+3v3Fgk9KOj3HFRxIkkBgzPX9jlVTRGcd7AiA0ulQgG7XU/gI4c+KdHoIPqzm2Zi eVsB6/oM3yfSQ== Received: from [IPV6:2a03:b580:afbb:9101:c452:7d7e:87de:9de9] (unknown [IPv6:2a03:b580:afbb:9101:c452:7d7e:87de:9de9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA id 43C2C11D5E for ; Sun, 22 Jun 2025 11:54:30 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------rgmyKFhyRYkPigvXVojz8mJu" Message-ID: Date: Sun, 22 Jun 2025 11:55:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pg_restore Question To: pgsql-admin@lists.postgresql.org References: Content-Language: en-US From: vrms In-Reply-To: X-NetCologne-Spam: L X-Rspamd-Queue-Id: 43C2C11D5E X-Spamd-Bar: - X-Rspamd-Action: no action List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------rgmyKFhyRYkPigvXVojz8mJu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit the bash history might give you an idea. You could not find anything though whether you did a restore from within the psql console, but that has a history too. On 21.06.25 12:10, Edwin UY wrote: > Hi, > > Without access to the dumpfile or log file, is there any way to check > whether a database has been restore either by pg_restore or other means? > > Regards, > Edd > > --------------rgmyKFhyRYkPigvXVojz8mJu Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
the bash history might give you an idea.
You could not find anything though whether you did a restore from within the psql console, but that has a history too.



On 21.06.25 12:10, Edwin UY wrote:
Hi,

Without access to the dumpfile or log file, is there any way to check whether a database has been restore either by pg_restore or other means?

Regards,
Edd


--------------rgmyKFhyRYkPigvXVojz8mJu--