ioltas

The bar to merge a patch that would break on-disk format is so high that it’s really impossible to reach it ;)

More seriously, we care a lot about the format of the 8k pages to ease upgrade paths as much as possible.

I’ve met Simon for the first time in Tokyo in 2009 for a birthday related to JPUG (Japan PostgreSQL User Group) when hot standby was getting integrated into the upstream project. I saw him last time in Prague three months ago, and we have joked about a few things while discussing about life and how things were going on as I did not go to the Postgres Europe conference for 6~7 years.

The community has lost a member, and many people have lost a friend. That’s so sudden. My thoughts go to his family and people who knew him. I’m so sad. RIP, Simon.

I’ll try to do something about that tomorrow, saw your ticket.

There are hooks for the planner and the executor, so you could force their hand quite easily with a plan extracted from a previous EXPLAIN. Being able to pass a plan at protocol level would be more efficient, for sure. I’ve worked on Postgres-XC and somewhat Postgres-XL, and that’s something that we wanted to do to generate a plan on one node, and push down the compiled plan down to other nodes to avoid the overhead of the plan computation. This stuff did that for snapshots and a few more things with an extension of the protocol.

Thanks, glad to hear some good feedback.

I’ve been doing maintenance and bug fixes for this module for over 18 months now (last commit on HEAD seems to be mine), managing the last two releases. If you have questions and/or feedback, feel free.

Note that this one mentions 借地料, meaning that you are not an owner of the land, but the government is lending it to you for a yearly fee of 220,000 yens.

It's been argued a few times that we should have the possibility to make an index invalid on sight with a proper ALTER INDEX command, yes.

FWIW, amcheck can be useful but I am not 100% sure that it can detect all the broken cases either.

mutt + mbsync with a local copy is also a nice combination.

Discussions within the core team are done on a private mailing list, so we'll know the status of things with a public announcement. Committers and contributors have no view of what gets discussed there, except if you are of course directly attached in CC of a given thread, and of course except if you are a committer also part of the core team. Four members of the current core team are committers.