Re: postgres wal log configuration question

From: Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com>
To: Rui DeSousa <rui(at)crazybean(dot)net>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: postgres wal log configuration question
Date: 2019-05-09 12:32:31
Message-ID: CA+M0sHGsvHdP-c6ZZeeefy79fobFg5TaUBwZ9BqBCB=1rCfGwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello Rui,

My apologies for delayed response.

Thank you so much for the information, it was helpful. another question I
Have is , is there anyway to control wal segment naming format. wal
segment file is not generating in sequential format.

On Tue, May 7, 2019 at 10:36 AM Rui DeSousa <rui(at)crazybean(dot)net> wrote:

>
>
> On May 7, 2019, at 10:58 AM, Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
>
>
>>
>> how do i understand the output ? Is this wal segment name ? If yes, when
>> i look at wal log location i do see below output. how do i correlate query
>> output with os command output ?
>>
>> postgres=# select pg_switch_wal();
>> pg_switch_wal
>> ---------------
>> C/E000158
>> (1 row)
>>
>>
> Use pg_walfile_name(); i.e.
>
>
> enso=# select pg_switch_wal();
> pg_switch_wal
> ---------------
> 29CF/4D14B48
> (1 row)
>
> enso=# select pg_walfile_name('29CF/4D14B48');
> pg_walfile_name
> --------------------------
> 00000001000029CF00000000
> (1 row)
>
>
>
>
> enso=# select pg_walfile_name(pg_switch_wal());
> pg_walfile_name
> --------------------------
> 00000001000029CF00000001
> (1 row)
>
>
>
>
>

--

*Regards,#! Pavan Kumar----------------------------------------------*-
*Sr. Database Administrator..!*
*NEXT GENERATION PROFESSIONALS, LLC*
*Cell # 267-799-3182 # pavan.dba27 (Gtalk) *
*India # 9000459083*

*Take Risks; if you win, you will be very happy. If you lose you will be
Wise *

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Pavan Kumar 2019-05-09 12:34:31 Re: pg_receivewal configuration issues
Previous Message Laurenz Albe 2019-05-09 11:42:06 Re: LDAP authentication failed