Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: ovsqlite (Julien ?LIE)
2. Re: Overview methods and rebuild documentation (Julien ?LIE)
3. Re: ovsqlite (Julien ?LIE)
4. Re: ovsqlite (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Thu, 24 Dec 2020 10:43:47 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Bo,
>> Article lines processed 3252700
>> Articles dropped 57
>> Overview index dropped 2673
>>
>> I usually have the same numbers for articles dropped and overview
>> index dropped. Maybe the difference is normal for the first run on
>> a new overview database built with makehistory? (I can't tell as I
>> do not know what was dropped exactly.)
>
> No idea. The expiration logic is mostly copied from ovdb. I tested it
> by removing the oldest 1/10 of each group's articles with sm -d
> before running expireover, and it seemed to remove exactly the right set
> of article rows from the database. (This was with cnfs and no group-based
> expiration.)
The 2nd run of ovsqlite expiry worked as usual (same number for articles
and overview index dropped).
I looked into my news.daily archives and found out a reassuring news
about the 1st run.
Last time I did it was after a change of news server. The 1st run of
expireover with tradindexed on a fresh new overview database (generated
during the transfer of articles via innxmit) looked like:
expireover start mardi 9 mai 2017, 04:15:27 (UTC+0200):
Article lines processed 2936398
Articles dropped 959
Overview index dropped 2347
and afterwards, articles and overview index dropped were identical.
So far so good then!
--
Julien ?LIE
??Ils ont refus? une offre de Normand??!??? (Ast?rix)
------------------------------
Message: 2
Date: Thu, 24 Dec 2020 10:59:50 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Overview methods and rebuild documentation
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Bo,
>> => OK with that new "OVERVIEW REBUILD" section ?
>
> Maybe mention
>
> ctlinnd renumber ""
>
> for when you want to be extra sure that the active file and the overview are
> in sync?
On second thoughts, it does not do harm to add that. Especially as a
check to do, and for people not to be surprised of the automatical
renumbering.
=item 7.
Starting INN and checking the logs to make sure everything is fine.
You will normally notice that the F<active> file is renumbered
(B<rc.news> takes care of that when run after an overview rebuild;
otherwise, manually run C<ctlinnd renumber "">).
--
Julien ?LIE
??Quousque tandem???? (Cic?ron)
------------------------------
Message: 3
Date: Thu, 24 Dec 2020 11:48:21 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Bo,
>> I see that the removal of a newsgroup is deferred until the next expiration,
>> which is a good thing (preventing an error in a control message or manually
>> with ctlinnd).
>
> Actually, it's because removing thousands of rows from the article table
> could take some time and shouldn't be allowed to block regular operations.
>
> Adding a new group does NOT undelete a previous one with the same name.
> I checked carefully what ovdb does in this situation and implemented
> the closest equivalent.
Indeed. I have just tested two successive removals and re-creations:
sqlite> select * from groupinfo where groupid>618;
619|1|3|3|0|1|trigofacile.test6|y
620|3|3|1|0|2|trigofacile.test6|y
621|1|0|0|0|0|trigofacile.test6|y
> Manual undeletion would be a lot easier with ovsqlite than with ovdb,
> since you get a free SQL command line tool with each SQLite installation.
Which is a point to add to the advantages of ovsqlite!
I am really fond of that SQL command line tool to explore the database!
Reinstating a newsgroup removed by error is very simple with that.
We'll now need ovspool for article storage :-)
--
Julien ?LIE
? Utiliser vi n'est pas un p?ch?, c'est une punition. Car souvenez-vous
que vi-vi-vi est l'?diteur de la B?te. ? (Stallman, Church of Emacs)
------------------------------
Message: 4
Date: Thu, 24 Dec 2020 12:57:03 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
> We'll now need ovspool for article storage :-)
sqlitespool I meant!
--
Julien ?LIE
??Farpaitement?!?? (Ob?lix)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 126, Issue 19
********************************************
