From: | Rui DeSousa <rui(at)crazybean(dot)net> |
---|---|
To: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: postgres wal log configuration question |
Date: | 2019-05-09 14:16:53 |
Message-ID: | DF39D2B0-2FAC-47CE-AB03-959BB9012A7A@crazybean.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On May 9, 2019, at 8:32 AM, Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
>
> is there anyway to control wal segment naming format. wal segment file is not generating in sequential format.
Not really; however the file names are sequential based on the timeline and log sequence. If you change the WAL segment size then the WAL file name sequence will change; i.e. 16MB vs 128MB WAL files will generate different sequences.
Here’s a article that covers the three parts of the filename; timeline_id, block id, and segment id:
https://paquier.xyz/postgresql-2/postgres-9-3-feature-highlight-pg_xlogdump/ <https://paquier.xyz/postgresql-2/postgres-9-3-feature-highlight-pg_xlogdump/>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Schneider | 2019-05-09 19:46:32 | Re: Query on pg_stat_activity table got stuck |
Previous Message | Tom Lane | 2019-05-09 14:03:04 | Re: How to create a postgres user that auth by AUTH_REQ_MD5 |