Re: Xlogdump compiling error : undefined reference to `ber_sockbuf_io_udp'

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Adarsh Sharma <eddy(dot)adarsh(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Xlogdump compiling error : undefined reference to `ber_sockbuf_io_udp'
Date: 2014-02-14 06:23:06
Message-ID: CAB7nPqSoyLza3nxZ_PAALM1TgMcf1adY6qFJ51qq7mObcvdF-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 14, 2014 at 3:14 PM, Adarsh Sharma <eddy(dot)adarsh(at)gmail(dot)com> wrote:
> Yes. Able to retrieve table names now.
>
> I am reviewing the xlogdump output. Is dere any way where i can understand
> what is the meaning of these keywords in it.
>
> [root(at)1002 tmp]# xlogdump pg_xlog/* > fullanalysis.txt
> [root(at)1002 tmp]# cat fullanaysis.txt | awk '{print $7}' | sort | uniq
> XLP_BKP_REMOVABLE
> bkpblock[1]:
> bkpblock[2]:
> commit_compact
> create
> delete:
> heap2_multi_insert:
> hot_update:
> inplace:
> insert_leaf:
> insert_upper:
> newpage:
> newroot:
> offset
> reuse_page:
> seq
> split_l:
> split_l_root:
> split_r:
> split_r_root:
> standby
> update(init):
> update:
Even if it is easy to guess to which WAL operations all those terms
refer to, referring to the source code is easier IMO:
https://github.com/snaga/xlogdump/blob/master/xlogdump_rmgr.c
Regards,
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martin Terjan 2014-02-14 09:08:53 CET ERROR: requested WAL segment has already been removed
Previous Message Adarsh Sharma 2014-02-14 06:14:14 Re: Xlogdump compiling error : undefined reference to `ber_sockbuf_io_udp'