upgrade – Drop tables but space not claimed in postgres 12

I have upgraded Postgresql 9.5 to Postgresql 12.4 a few days back using pg_upgrade utility with link (-k) option.

So basically I am having two data directories i.e. One is old data directory (v9.5) and the current one in running state (v12.4).

Yesterday I have dropped two tables of size 700MB and 300MB.

After connecting to postgres using psql utility I can see database size whose tables was dropped got decreased (with l+ ) but what is making me worry is that only a few MBs have been freed from storage partition.

I have checked if any deleted open file is there on OS level using lsof but there is none. I have run vacuumdb only on that database but no luck

Looking for the solution.

I upgraded from 14.04 to 16.04 (do-release-upgrade) with mysql version held. When trying to upgrade to 18.04, please install updates

I was able to upgrade using do-release-upgrade from 14.04 to 16.04, while holding mysql version. When I try to upgrade to 18.04 I get error to install updates for release before upgrading.
Is it possible to upgrade with mysql still on hold?

magento2 – X-Frame-Options SAMEORIGIN not working after upgrade to 2.4.1

I just upgraded from 2.3.4 to 2.4.1 , before there is no issue when load content using iframe, but now there is always an error message:

Refused to display 'http://test.m2.local/test/index/test/' in a frame because it set 'X-Frame-Options' to 'deny'.

Refused to display '<URL>' in a frame because it set multiple 'X-Frame-Options' headers with conflicting values ('DENY, SAMEORIGIN'). Falling back to 'deny'.

the app/etc/env.php already included SAMEORDIGIN configuration

'x-frame-options' => 'SAMEORIGIN',

before i upgrade to 2.4.1, i duplicated the 2.3.4 instance and hosted in different sub domain in the same server, but it does not get any error

configuration – MariaDB doesn’t read all options from /etc/mysql/conf.d/ after upgrade

I am using Ubuntu 20.04LTS. I upgraded Mariadb 10.5.5 to 10.5.8 using mariadb’s own repositories. After upgrade I noticed API server was unable to connect to DB server through private network. After some tinkering, I realized mariadb is no longer reading bind-address from /etc/mysql/conf.d/customizations.cnf and was listening to 127.0.0.1 instead of 0.0.0.0. Then I proceeded to adding bind-address to /etc/mysql/my.cnf and then it worked again.

/etc/mysql/mariadb.cnf is the config used. It is symlinked to /etc/mysql/my.cnf. Which contains line !includedir /etc/mysql/conf.d/
All the other configurations such as innodb_buffer_pool_size are still read from file: /etc/mysql/conf.d/customizations.cnf, but bind-address is not. Why is that? And yes its under [mysqld].

My /etc/mysql/conf.d/customizations.cnf:

[mysqld]
bind-address = 0.0.0.0
skip_name_resolve=1
innodb_buffer_pool_size=20G
max_connections=550

[mariadb]
log_error=/var/log/mysql/mariadb-errors.log

upgrade – ERROR: permission denied for relation pg_class SQL state: 42501

Trying to execute the below query: but gettting permission denied for pg_class error, tried to grant privileges to all tables, sequences and functions but no grants warnings have been issued. Please help to resolve this. or suggest how to remove usage of reg* datatypes
delete FROM pg_catalog.pg_class as c
using pg_catalog.pg_namespace as n, pg_catalog.pg_attribute as a
WHERE c.oid = a.attrelid
AND NOT a.attisdropped
AND a.atttypid IN (‘pg_catalog.regproc’::pg_catalog.regtype,
‘pg_catalog.regprocedure’::pg_catalog.regtype,
‘pg_catalog.regoper’::pg_catalog.regtype,
‘pg_catalog.regoperator’::pg_catalog.regtype,
‘pg_catalog.regconfig’::pg_catalog.regtype,
‘pg_catalog.regdictionary’::pg_catalog.regtype)
AND c.relnamespace = n.oid
AND n.nspname NOT IN (‘pg_catalog’, ‘information_schema’);

openstack – How do I perform a release upgrade on a server running Landscape?

I’m attempting to perform a release upgrade from 18.04LTS to 20.04LTS, on my server running Landscape.

The upgrade is blocked due to

An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu

According to the upgrade log, the unofficial software is the landscape server (if I’m interpreting “Foreign” correctly):

2020-11-18 19:17:24,416 DEBUG Foreign: landscape-client landscape-common landscape-hashids landscape-server landscape-se
rver-quickstart libjs-yui3-common libjs-yui3-full libjs-yui3-min python-convoy python-pyjwkest python-pyoidc python-stor
m python-stripe python-talisker python-txamqp python-txaws python-txjuju python-txlongpoll

I also see later in the log that

2020-11-18 19:17:56,869 DEBUG blacklist expr '^postgresql-.*(0-9)(0-9).*' matches 'postgresql-10-debversion'
2020-11-18 19:17:56,869 DEBUG The package 'postgresql-10-debversion' is marked for removal but it's in the removal black
list
2020-11-18 19:17:56,884 ERROR Dist-upgrade failed: 'The package 'postgresql-10-debversion' is marked for removal but it
is in the removal blacklist.'
2020-11-18 19:17:56,884 DEBUG abort called

so it’s possible the “unofficial software” warning is a red herring.

Has anyone successfully done a release upgrade on a server running Landscape?