Re: pg_restore Question

From: Edwin UY <edwin(dot)uy(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_restore Question
Date: 2025-06-22 10:52:00
Message-ID: CA+wokJ_11i8tp-oDMkt_FRcx8xJV7ZOy2QWW80-fWk_bdGHQgw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Yes, Samurai Jack, I mean Ron --- just kidding. That is my preference too.
When you work with several people who are 'Senior' DBA, it's difficult to
go to a debate / argument of sort that we should be doing it like this :(
Will continue to check things around.
Kinda hoping there are some kind of timestamps when a table / index gets
created.

P.S.:
I really wish I can properly learn PostgreSQL hands-on in the real world as
a remote intern somewhere.

On Sun, Jun 22, 2025 at 9:58 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> This is why I do all backups, restores, upgrades, etc through cron.
>
> On Sat, Jun 21, 2025 at 8:59 AM Furkan Shaikh <fs626261(at)gmail(dot)com> wrote:
>
>>
>> -
>>
>> *No Definitive Proof:* Without logs, you cannot get a timestamped log
>> entry saying "pg_restore started/finished." All these methods provide
>> indirect evidence.
>> -
>>
>> *Requires Prior Knowledge:* Most effective indicators rely on you
>> having some memory or previous records of the database's state (e.g.,
>> typical sequence values, expected bloat, average last-vacuum times).
>> -
>>
>> *Other Causes:* Some of these patterns (like recent statistics) could
>> also be caused by an aggressive VACUUM FULL, a major data import
>> through other means, or an application bug that resets sequences.
>>
>> Conclusion
>>
>> The most reliable indicators without direct logs are a *sudden and
>> uniform resetting of last_vacuum/last_analyze timestamps to NULL or very
>> recent values across all user tables*, combined with a potential change
>> in object OIDs (if you tracked them) or unexpected sequence values. If you
>> see most of your tables
>>
>> On Sat, 21 Jun, 2025, 3:41 pm Edwin UY, <edwin(dot)uy(at)gmail(dot)com> 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
>>>
>>>
>>>
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron Johnson 2025-06-22 16:57:23 Re: pg_restore Question
Previous Message vrms 2025-06-22 10:00:30 Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0