Re: Sudden spike in WAL

From: Siraj G <tosiraj(dot)g(at)gmail(dot)com>
To: Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Sudden spike in WAL
Date: 2024-06-30 08:48:19
Message-ID: CAC5iy61+V+SjriR+fuqzk2Ud1TegD2W2uzKeraJ+Sv59mh+ftg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thank you Achilleas.

On Sun, Jun 30, 2024 at 2:40 AM Achilleas Mantzios <
a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:

> Στις 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(dot)g(at)gmail(dot)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(at)gmail(dot)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(dot)g(at)gmail(dot)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: image.png]
>>>> Regards
>>>> Siraj
>>>>
>>> --
> Achilleas Mantzios
> IT DEV - HEAD
> IT DEPT
> Dynacom Tankers Mgmt (as agents only)
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Veerendra Pulapa 2024-07-01 12:26:15 Re: Urgent: Segmentation Fault in PostgreSQL postmaster Process
Previous Message Ron Johnson 2024-06-30 06:48:07 Re: Strange "permission denied" errors on pg_restore