On Sun, Feb 24, 2019 at 5:48 PM <ivan.kabaivanov(a)gmail.com&gt; wrote: You have ran into a known bug, which is not documented anywhere except for comments in the code, so I do not provide a link to a bug. Feel free to report it if you want. The bug is in the case of 'Local' database and 'Manual' provisioning. In this case (which is what you want to do), database hostname is 'localhost'. Elsewhere in the code, in more than one place, we have heuristics that say that if database hostname is 'localhost', we "own" it, and can do admin stuff on it. This includes the above uuid-ossp extension. A trivial workaround, which might be also what we'll eventually decide to suggest even if you open a bug, is to not provide 'localhost', but a different name or IP address that points at the local machine. If you do not want to rely on a particular IP address, you can even add to the '127.0.0.1' line in /etc/hosts another name (e.g. 'localpg' or whatever) and use that - the check is purely textual. If you want, you can search the code for all occurrences of "'localhost'". You'll get a few "false positives", but this will be a good start. One reason this isn't easy to fix is that we do not save anywhere, after engine-setup finished, the answer to the question "Automatically provision pg?". So a later run has no-way to know if it's 'localhost' and 'Automatic' or 'localhost' and 'Manual'. Since almost all users use 'Automatic', and among those that use 'Manual' almost all use also 'Remote', very few actually run into the bug, like you. To fix it we need to save the answer (easy), but also consider what to do if we do not (yet) have it, as we only _ask_ it during initial setup, not upgrade. So a theoretical fix can be to proactively ask on upgrade "DB host is 'localhost', was it automatically provisioned by Setup in the past?". Since this is so ugly that no-one will ever want it, we'll probably have to use something else, e.g. allow a user (like you) to set in some conf file somewhere 'db is manually provisioned, do not touch it'. -- Didi

On Mon, Feb 25, 2019 at 8:19 PM <ivan.kabaivanov(a)gmail.com&gt; wrote: Thanks for the report! Now filed [1], ~5 years too late, but hopefully better late than never... [1] https://bugzilla.redhat.com/show_bug.cgi?id=1683126 -- Didi