agora inbox for pgsql-admin@postgresql.org  
help / color / mirror / Atom feed
From: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Sudden spike in WAL
Date: Sun, 30 Jun 2024 00:10:36 +0300
Message-ID: <8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com> (raw)
In-Reply-To: <CADg2TZ+iQv_vk4NUQt_vCsWFQDrEo6DLROp_s7vTJ+Sj+kztXA@mail.gmail.com>
References: <CAC5iy61sCxqpO=srpBG9ynC_BWy_mu1wxiagX7Yn9_ddkanPMA@mail.gmail.com>
	<CADg2TZJRshKTa7mD9ZfV5Wua25DPVxgKZoa=TWVAv9FrJitxnA@mail.gmail.com>
	<CAC5iy62bVkFBEmxFXF6vr0-jLKFq+fLHcxoXvf5YziVMWQCSaw@mail.gmail.com>
	<CADg2TZ+iQv_vk4NUQt_vCsWFQDrEo6DLROp_s7vTJ+Sj+kztXA@mail.gmail.com>

Στις 29/6/24 22:29, ο/η Mahesh mana έγραψε:
>
> Hi,
>
> it should from the time when your slave is down,pls check your slave .
>
> Not sure if there is a query to check that..
>
select sl.*,walz.* from pg_replication_slots sl, pg_ls_waldir() walz 
where walz.name=pg_walfile_name(sl.confirmed_flush_lsn);

provided there was activity post the last flushed WAL file or wal switch 
, the above would be an estimation, of when the replication stopped working.

>
> On Sun, Jun 30, 2024, 12:48 AM Siraj G <tosiraj.g@gmail.com> wrote:
>
>     Hi Mahesh
>
>     Yes, I noticed an inactive replication slot.
>
>     select * From pg_replication_slots where not active;
>                      slot_name                  |  plugin      |
>     slot_type | datoid |    database    | temporary | active |
>     active_pid | xmin | catalog_xmin | restart_lsn  |
>     confirmed_flush_lsn | wal_status | safe_wal_size
>     ---------------------------------------------+------------------+-----------+--------+----------------+-----------+--------+------------+------+--------------+--------------+---------------------+------------+---------------
>      pgl_marketing_prod_provider_marketin3444436 | pglogical_output |
>     logical   |  16648 | marketing_prod | f         | f      |        
>        |      |    244033832 | E0C/DABEE880 | E0C/DABF1870        |
>     extended   |
>     (1 row)
>
>     How do I see the timestamp it became inactive?
>
>     On Sun, Jun 30, 2024 at 12:24 AM Mahesh mana
>     <maheshbabumms12@gmail.com> wrote:
>
>         Hi,
>
>         Please check if you have any inactive replication slot.
>
>         Thanks,Mahesh.
>
>
>         On Sun, Jun 30, 2024, 12:22 AM Siraj G <tosiraj.g@gmail.com>
>         wrote:
>
>             Hello!
>
>             I am trying to figure out why we had a sudden spike in WAL
>             (on 12th Jun at around 6:30pm IST). The storage has not
>             got back to its original state since then.
>
>             Please assist if there is a way we can find it out. The
>             instance is a GCP cloud managed and PgSQL version is 13.
>
>             Please see the spike below:
>
>             image.png
>             Regards
>             Siraj
>
-- 
Achilleas Mantzios
  IT DEV - HEAD
  IT DEPT
  Dynacom Tankers Mgmt (as agents only)

Attachments:

  [image/png] image.png (39.9K, ../8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com/3-image.png)
  download | view image

view thread (6+ messages)  latest in thread

Message-ID: <8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com>
Permalink:  ../8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com/
Also on:    postgresql.org/message-id/8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: a.mantzios@cloud.gatewaynet.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Sudden spike in WAL
  In-Reply-To: <8d84bfb9-8a2d-4467-a93f-c39fac45ebe2@cloud.gatewaynet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox