public inbox for [email protected]
help / color / mirror / Atom feedFrom: Célestin Matte <[email protected]>
To: [email protected]
To: Magnus Hagander <[email protected]>
Cc: [email protected]
Subject: Re: Adding a readme to the pgarchives repo
Date: Fri, 20 Jun 2025 11:59:56 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEzUUkBuJG9UGhhBn6L7OfPqSjczmt0Ac1sRK1zELJ71Sg@mail.gmail.com>
References: <CAGECzQSaRNp3GW4yCqF3oucHji6dKK4DjVn-nfan9fKaonhPOA@mail.gmail.com>
<CAGECzQTZKPqZ2_xjCybicZYV4OWO6oq5NLiDtQ9eoc65NuO_fA@mail.gmail.com>
<CABUevExSAybE1Grq3Ka6OgYax5ut1ajEfUjUY1XKcuXdfrdsSg@mail.gmail.com>
<CAGECzQTOgdA_7RbL92tjPakyLEXPaWmRLzwQAV7k-=xmkQgnKQ@mail.gmail.com>
<CAGECzQRtfyd6WNAzF0Ut9fTq3rPrET3NEy-y75QzeFU57RcwsQ@mail.gmail.com>
<CAGECzQQsYE-pJK7BG6mk1pYFJ5afs6GU_Pf98vd_mMNe6eSRKA@mail.gmail.com>
<CABUevEzUUkBuJG9UGhhBn6L7OfPqSjczmt0Ac1sRK1zELJ71Sg@mail.gmail.com>
Hello,
(Unsure what the beginning of the conversation and the patches are, I don't seem to see them on the list)
> The change in schema.sql to add subscriber_access should surely be a separate commit, it's not part of adding a README file. (in fact, many thing are not adding a README file). So I'll separate thato ne out right away. That said, this one is also caught in the limbo between some things being as migrations and some things not, that reall needs to get cleaned up :/ Celestin worked on that at some point, I think, and I need to get back to properly reviewing that.
Yes, I actually already fixed subsciber_access and it's still waiting for integration, see https://www.postgresql.org/message-id/a99938be-c9ad-8d94-0a16-8305e6391f1e%40cmatte.me (beginning of thread here: https://www.postgresql.org/message-id/[email protected] )
> I'm not sure how much sense it makes to load data from schema.sql. Wouldn't it be better with a dev_data entr?
I fixed the schema.sql mess here: https://www.postgresql.org/message-id/a31a7071-7338-4423-a8e5-16d70f19c2c8%40cmatte.me (beginning of thread here: https://www.postgresql.org/message-id/12eb75f0-3fc2-14f3-0931-4f29e145f182%40cmatte.me )
> Also, I don't think removing text search configuration completely from a dev install is the right way to go. All of this is definitely part of the system and if nothing else one would want to make not to accidentally *break* it in dev, thus they are needed.
Not sure if related, but I fixed search web front-end here: https://www.postgresql.org/message-id/[email protected]
@Jelte: I maintain a version that's integrating my patches that fix the various issues encountered around a new deployment here: https://gitlab.com/cmatte/pgarchives/
I wrote an install procedure (which may not be fully up-to-date anymore) here: https://gitlab.com/cmatte/pglister/-/blob/master/INSTALL.md
and made an ansible script to install the various components here: https://gitlab.com/cmatte/ansible-pglister
Hopefully my patches all get reviewed and integrated at some point. As a reminder, I made a list to simplify that here: https://www.postgresql.org/message-id/[email protected]
--
Célestin Matte
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Adding a readme to the pgarchives repo
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox