| From: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> |
|---|---|
| To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PITR and instance without any activity |
| Date: | 2023-01-11 10:26:00 |
| Message-ID: | dd87f8f4-924f-7a10-fab6-5f41b08e4f17@anayrat.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/9/23 11:23, Torsten Förtsch wrote:
> On Mon, Jan 9, 2023 at 10:59 AM Adrien Nayrat
> <adrien(dot)nayrat(at)anayrat(dot)info <mailto:adrien(dot)nayrat(at)anayrat(dot)info>> wrote:
>
>
> * We can't perform PITR on a cluster without any activity since 13
> * It seems creating restore point doesn't record a timestamp in wal.
>
> I have a cron job that runs this every 5 minutes:
>
> SELECT txid_current() WHERE
> (pg_last_committed_xact()).timestamp+'5min'::INTERVAL < now()
>
> Combine that with a suitable value for archive_timeout.
Hello,
I don't get how it could be useful ?
When we perform PITR, we don't know if there was activity or not.
--
Adrien NAYRAT
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2023-01-11 12:54:03 | Re: Disallow execution of shell commands from psql |
| Previous Message | Vikas Sharma | 2023-01-11 08:43:09 | Re: Best opensource Postgresql monitoring tool |