Hi,
On 2026-06-02 20:36:08 +0300, Nazir Bilal Yavuz wrote:
> You are right, I confirm that this approach solves the problem and I
> think this solution makes sense.
Cool.
> From another thread:
> > I find postgresql-ci.yml a bit long, how about postgres-ci.yml or pg-ci.yml?
>
> I am okay with both but my choice would be postgres-ci.yml.
Due to Peter's input, I went with pg-ci.yml for now. If others want to weigh
in...
I did some more changes:
- Made Meson (64-bit) run address sanitizer, it's about 2 minutes faster
- Rephrased the README
This is currently done in a separate commit for easier review here, but I
think I'd merge it before pushing.
- Made the cirrus-ci removal commits more complete
- changed the "name" to "CI for PostgreSQL", the "GitHub Actions" part was
seemed pointless
- added a small amount of comments at the top of pg-ci.yml
- Some general commit message and comment polishing
- renamed "Windows - VS - Meson & ninja" to "Windows - Visual Studio" the
former was a bit too long once running and truncated. Better suggestions
welcome.
- changed the container URL to ghcr.io/anarazel/pg-vm-images/main, I replaced
the main branch now.
Think this is pretty close to committable. There's loads more to do, but
getting some CI back seems pretty important, we can iterate subsequently.
Greetings,
Andres Freund
