Bug 1425905 - PostgreSQL Wal Sender Process Memory is Ballooning from DB Vacuum Command
Summary: PostgreSQL Wal Sender Process Memory is Ballooning from DB Vacuum Command
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.7.5
Assignee: Nick Carboni
QA Contact: Alex Newman
URL:
Whiteboard: database
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-22 17:46 UTC by myoder
Modified: 2020-05-14 15:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-17 19:39:29 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2924451 0 None None None 2017-02-22 17:50:14 UTC

Description myoder 2017-02-22 17:46:37 UTC 
Description of problem: 
The auto vacuum scripts that have been implemented via the appliance console are causing the postgres wal sender process memory to balloon.  This is happening every Saturday at 3:00am when the vacuum full tables is run.


VACUUM FULL VERBOSE vim_performance_states;
INFO:  vacuuming "public.vim_performance_states"
INFO:  "vim_performance_states": found 0 removable, 74842405 nonremovable row versions in 5479519 pages
DETAIL:  0 dead row versions cannot be removed yet.
CPU 106.67s/114.74u sec elapsed 685.80 sec.
VACUUM
Time: 1631870.671 ms
periodic vacuum full completed at Sat Feb 18 03:27:36 PST 2017

Top output of the wal process:
20890 postgres  20   0 13.561g 4.084g   6456 S   0.0 26.3 118:53.65 postgres

Version-Release number of selected component (if applicable):
5.7.0.17

How reproducible:
Always


Steps to Reproduce:
1. Run "VACUUM FULL VERBOSE vim_performance_states;" on the vmdb
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.