pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSudden spike in WAL
6+ messages / 3 participants
[nested] [flat]
* Sudden spike in WAL
@ 2024-06-29 18:52 Siraj G <tosiraj.g@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Siraj G @ 2024-06-29 18:52 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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
Attachments:
[image/png] image.png (39.9K, ../../CAC5iy61sCxqpO=srpBG9ynC_BWy_mu1wxiagX7Yn9_ddkanPMA@mail.gmail.com/3-image.png)
download | view image
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Sudden spike in WAL
@ 2024-06-29 18:54 Mahesh mana <maheshbabumms12@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Mahesh mana @ 2024-06-29 18:54 UTC (permalink / raw)
To: tosiraj.g@gmail.com; +Cc: pgsql-admin@lists.postgresql.org
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: image.png]
> Regards
> Siraj
>
Attachments:
[image/png] image.png (39.9K, ../../CADg2TZJRshKTa7mD9ZfV5Wua25DPVxgKZoa=TWVAv9FrJitxnA@mail.gmail.com/3-image.png)
download | view image
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Sudden spike in WAL
@ 2024-06-29 19:18 Siraj G <tosiraj.g@gmail.com>
parent: Mahesh mana <maheshbabumms12@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Siraj G @ 2024-06-29 19:18 UTC (permalink / raw)
To: Mahesh mana <maheshbabumms12@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
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: image.png]
>> Regards
>> Siraj
>>
>
Attachments:
[image/png] image.png (39.9K, ../../CAC5iy62bVkFBEmxFXF6vr0-jLKFq+fLHcxoXvf5YziVMWQCSaw@mail.gmail.com/3-image.png)
download | view image
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Sudden spike in WAL
@ 2024-06-29 19:29 Mahesh mana <maheshbabumms12@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Mahesh mana @ 2024-06-29 19:29 UTC (permalink / raw)
To: tosiraj.g@gmail.com; +Cc: pgsql-admin@lists.postgresql.org
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..
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: image.png]
>>> Regards
>>> Siraj
>>>
>>
Attachments:
[image/png] image.png (39.9K, ../../CADg2TZ+iQv_vk4NUQt_vCsWFQDrEo6DLROp_s7vTJ+Sj+kztXA@mail.gmail.com/3-image.png)
download | view image
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Sudden spike in WAL
@ 2024-06-29 21:10 Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
parent: Mahesh mana <maheshbabumms12@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Achilleas Mantzios @ 2024-06-29 21:10 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Στις 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Sudden spike in WAL
@ 2024-06-30 08:48 Siraj G <tosiraj.g@gmail.com>
parent: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
0 siblings, 0 replies; 6+ messages in thread
From: Siraj G @ 2024-06-30 08:48 UTC (permalink / raw)
To: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>; +Cc: pgsql-admin@lists.postgresql.org
Thank you Achilleas.
On Sun, Jun 30, 2024 at 2:40 AM Achilleas Mantzios <
a.mantzios@cloud.gatewaynet.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.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: image.png]
>>>> Regards
>>>> Siraj
>>>>
>>> --
> Achilleas Mantzios
> IT DEV - HEAD
> IT DEPT
> Dynacom Tankers Mgmt (as agents only)
>
>
Attachments:
[image/png] image.png (39.9K, ../../CAC5iy61+V+SjriR+fuqzk2Ud1TegD2W2uzKeraJ+Sv59mh+ftg@mail.gmail.com/3-image.png)
download | view image
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-06-30 08:48 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-06-29 18:52 Sudden spike in WAL Siraj G <tosiraj.g@gmail.com>
2024-06-29 18:54 ` Mahesh mana <maheshbabumms12@gmail.com>
2024-06-29 19:18 ` Siraj G <tosiraj.g@gmail.com>
2024-06-29 19:29 ` Mahesh mana <maheshbabumms12@gmail.com>
2024-06-29 21:10 ` Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
2024-06-30 08:48 ` Siraj G <tosiraj.g@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox