Re: medawiki plugin - Mailing list pgsql-www
| From | Magnus Hagander |
|---|---|
| Subject | Re: medawiki plugin |
| Date | |
| Msg-id | CABUevEy_xXwXEjTD10NHQO4E-D2u_gvFVzrMvApY1iu3J8F5sg@mail.gmail.com Whole thread Raw |
| In response to | Re: medawiki plugin (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>) |
| List | pgsql-www |
On Sun, May 26, 2024 at 5:17 PM Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote:
Hi Jeremy!
On 5/26/24 02:31, Jeremy Schneider wrote:
> Out of curiosity, has anyone here heard of the Semantic-MediaWiki (SMW)
> plugin?
>
> https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki
>
> It lets you store and query data within the pages of a wiki. ISTM that
> it gives you the change tracking of a wiki alongside the flexible
> querying of a database. Might be some interesting use cases for
> something like this. Wondering if this is super obscure and unheard of,
> or if someone here knows anything about it?
no idea on that one - are you suggesting we should install that plugin
or is that more of a question on what people think of the concept behind
it? If it's the later, not sure -www is the right place to ask...
I would add to that that any plugins not packated up by/for debian require a *very* strong argument for doing, since it means we have to handle all security patching and such manually for it.
Doesn't mean it's impossible, just that the maintenance cost is orders of magnitude higher, so the benefits had better be too.
But to answer the original question, nope, I've never heard of this particular extension - but I'm by no means a mediawiki expert :)
> PS... happened to check https://wiki.postgresql.org/wiki/Special:Version
> to see what plugins are already installed. So I guess we have a DB major
> version upgrade to run some time this year? 🙂 Who plans and runs the
> upgrade, and is the discussion on this public www list, where I could
> follow along and learn a bit about how it's done?
System upgrades are usually done by the postgresql
sysadmin/infrastructure team [1] but due to the large amount of systems
and the way our infrastrcture is maintained we have we don't usually
discuss individual upgrades or changes like this ahead of time (other
than a downtime notice if needed).
In the specific case of wiki.postgresql.org we will likely not only
upgrade the database (which is likely rather trivial) but also the
underlying OS and the mediawiki version when the time comes.
Well, you're almost right :) Looking at it it seems we did upgrade the OS without the database last time. So given the timing for when pg 12 goes out of support, doing the database separately I believe is on the todo list.
That said, I believe the reason it's lagging behind is that everybody is kind of worried about touching anything behind the wiki, since it's extremely fragile and can result in a lot of time spent debugging things. A postgres update *should* be safe, but the stack is very fragile.