Red Hat Bugzilla – Bug 1047125
[reports] upgrade: update ownership is slow and fills the log
Last modified: 2015-09-22 09:10 EDT
+++ This bug was initially created as a clone of Bug #1046676 +++ Description of problem: On upgrade from 3.2 to 3.3 with a local database, we change the ownership of all db objects from 'postgres' to 'engine_reports'. We do this by running 'pg_dump', searching the output for 'Owner postgres', then create a set of sql commands to change the ownership and run them, each in its own psql command. This has two problems: 1. pg_dump's output also goes to the log, and if the database is large, the log might feel up the disk. 2. Running each command in its own psql is slow Proposed solution: 1. We should add '-s' to pg_dump to dump only the schema, that's enough for that purpose 2. We should run all the SQL commands in a single psql command. This is less severe than bz #1046676 because the database in reports is not expected to be large.
So the log will list the table content? This is a blocker, since passwords will also appear. Yaniv
Yes, they appear obfuscated, but I agree it's a blocker.
verified on rhevm-reports-3.3.0-28.el6ev.noarch rhevm-dwh-3.3.0-28.el6ev.noarch see logs attached. /usr/bin/pg_dump -s rhevmreports
Created attachment 851496 [details] logs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0035.html