Notices by roland (roland@f.haeder.net)

@dj @shatterrealm Other non-pornographic educational image:

It is very easy to debunk the woke nonsense. Sure this called a lot of trolls, so I ignore (Friendica can do that) this thread.

#NSFW #Vagina

@shatterrealm Seem to troll heterosexuals and homosexuals alike? Sorry, look between your own legs, you'll find something like this:

... then you are a woman, your sex is female.

#Vagina #Lubricated #NSFW #Pussy #Anus #FemaleGenitalia

zdnet.com/article/why-mark-zuc…

@mk @p @djsumdog I can understand you both. On one hand, software X can migrate/upgrade its file structure (e.g. "binary format") by itself by running automatically some migration/upgrade script. These scripts can be bound to version numbers (when the upgrade takes place) so the user=admin isn't bothered by it. The "in-place" migration also forces the upgrade on the user=admin.

But it seems like #PostgreSQL seem to follow an other philosophy that says that administrators are the responsible persons and it should be in their full control when the migration/upgrade should take place. So they don't want to force the upgrade on the admin's decision-making progress and let him decide whenever it takes place.

So what would be the solution? A simple script like pg_upgrade.sh that the administrator can manually run or for those people like @mk is that the installer asks "Should pg_upgrade.sh run for your automatically?" and it is done then during upgrade.

@admin @anildash I have seen that they have named the account potus and not president_joe_biden. Is there a particular reason for this?

EDIT: Rephrased whole question.