RetroBBS - comp.databases.ingres - Re: Finding the last committed transaction using auditdb

Finding the last committed transaction using auditdb

<d4ae285b-95af-4cbe-8cf1-8bbf1ced81can@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=222&group=comp.databases.ingres#222

copy link Newsgroups: comp.databases.ingres

X-Received: by 2002:ac8:57d6:0:b0:2e0:68af:7c52 with SMTP id w22-20020ac857d6000000b002e068af7c52mr10256560qta.380.1649309643254;
Wed, 06 Apr 2022 22:34:03 -0700 (PDT)
X-Received: by 2002:a05:6808:2083:b0:2da:146e:cb2b with SMTP id
s3-20020a056808208300b002da146ecb2bmr5345512oiw.224.1649309642883; Wed, 06
Apr 2022 22:34:02 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.databases.ingres
Date: Wed, 6 Apr 2022 22:34:02 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=1.145.55.42; posting-account=uL8iyAoAAABmcpUSs5hxN0c_ls8MZOL5
NNTP-Posting-Host: 1.145.55.42
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d4ae285b-95af-4cbe-8cf1-8bbf1ced81can@googlegroups.com>
Subject: Finding the last committed transaction using auditdb
From: s.anderson.au@gmail.com (Steve)
Injection-Date: Thu, 07 Apr 2022 05:34:03 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 9

by: Steve - Thu, 7 Apr 2022 05:34 UTC

Hi folks

Is my understanding correct that auditdb will only show committed transactions?

That is, it will not show transactions in the journal which are yet to be committed? For example, transactions which begin in one journal and end in a subsequent journal.

Trying to understand how I find the last committed transaction in case of a failover.

Thanks
Steve

Re: Finding the last committed transaction using auditdb

<t2mn3v$1t35$1@gioia.aioe.org>

copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=223&group=comp.databases.ingres#223

copy link Newsgroups: comp.databases.ingres

Path: i2pn2.org!i2pn.org!aioe.org!ow2HZ3WUoSa7bUAoHqrJ8A.user.46.165.242.75.POSTED!not-for-mail
From: specially@processed.almost.meat (Roy Hann)
Newsgroups: comp.databases.ingres
Subject: Re: Finding the last committed transaction using auditdb
Date: Thu, 7 Apr 2022 12:57:35 -0000 (UTC)
Organization: Aioe.org NNTP Server
Message-ID: <t2mn3v$1t35$1@gioia.aioe.org>
References: <d4ae285b-95af-4cbe-8cf1-8bbf1ced81can@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="62565"; posting-host="ow2HZ3WUoSa7bUAoHqrJ8A.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: XPN/1.2.6 (Street Spirit ; Windows)
X-Notice: Filtered by postfilter v. 0.9.2

by: Roy Hann - Thu, 7 Apr 2022 12:57 UTC

Steve wrote:

> Hi folks
>
> Is my understanding correct that auditdb will only show committed
> transactions?

That is its default behaviour, yes.

> That is, it will not show transactions in the journal which are yet to
> be committed? For example, transactions which begin in one journal and
> end in a subsequent journal.
>
> Trying to understand how I find the last committed transaction in case
> of a failover.

If you have replicated iiacp.log as well as the journals iiacp.log will
show you when the archiver last ran. (It is possible the archiver has
been configured to run at timed intervals though (cp_timer), so you may
need to read the log carefully to discover when it last found something
to journal.)

Alternatively if the timestamp on the journal file is preserved you can
tell when it was last written.

You can then run auditdb with the -b flag specifying a time just before
the last archive cycle. You will probably only need to go back a
few seconds.

Roy

The world is no nursery. -- Sigmund Freud

devel / comp.databases.ingres / Re: Finding the last committed transaction using auditdb

Subject	Author
Finding the last committed transaction using auditdb	Steve
Re: Finding the last committed transaction using auditdb	Roy Hann