Postgres 9.6.6 on Ubuntu 16.04, lots of errors
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
We're running perfsonar on a group of our servers, and while doing some maintenance work found that we
- get giant logfiles under
/var/log/postgresql
- table bloat on the database of the perfsonar scheduler
I assume the toolkit is using table locking when it does ANYTHING on the database, and always cancels the autovacuum run:
2019-04-07 06:33:43 NZST [471-1] ERROR: canceling autovacuum task
2019-04-07 06:33:43 NZST [471-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
2019-04-07 06:34:33 NZST [981-1] ERROR: canceling autovacuum task
2019-04-07 06:34:33 NZST [981-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
A manual run of vacuum analyze roughly halved the use of disk space under /var/lib/postgresql/9.6/main/base/ ...
I've found several web pages talking about autovacuum tuning, but I'm wondering if it wouldn't make sense to disable autovacuum and run a vacuum analyze from a cron job.
Is there a best practice/recommendation for this kind of situation?
And maybe ask the perfsonar project to clean up their code in the long run ;}
locking postgresql-9.6 autovacuum
asked 1 min ago
tinktink
11615
add a comment |
We're running perfsonar on a group of our servers, and while doing some maintenance work found that we
- get giant logfiles under
/var/log/postgresql
- table bloat on the database of the perfsonar scheduler
I assume the toolkit is using table locking when it does ANYTHING on the database, and always cancels the autovacuum run:
2019-04-07 06:33:43 NZST [471-1] ERROR: canceling autovacuum task
2019-04-07 06:33:43 NZST [471-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
2019-04-07 06:34:33 NZST [981-1] ERROR: canceling autovacuum task
2019-04-07 06:34:33 NZST [981-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
A manual run of vacuum analyze roughly halved the use of disk space under /var/lib/postgresql/9.6/main/base/ ...
I've found several web pages talking about autovacuum tuning, but I'm wondering if it wouldn't make sense to disable autovacuum and run a vacuum analyze from a cron job.
Is there a best practice/recommendation for this kind of situation?
And maybe ask the perfsonar project to clean up their code in the long run ;}
locking postgresql-9.6 autovacuum
asked 1 min ago
tinktink
11615
add a comment |
We're running perfsonar on a group of our servers, and while doing some maintenance work found that we
- get giant logfiles under
/var/log/postgresql
- table bloat on the database of the perfsonar scheduler
I assume the toolkit is using table locking when it does ANYTHING on the database, and always cancels the autovacuum run:
2019-04-07 06:33:43 NZST [471-1] ERROR: canceling autovacuum task
2019-04-07 06:33:43 NZST [471-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
2019-04-07 06:34:33 NZST [981-1] ERROR: canceling autovacuum task
2019-04-07 06:34:33 NZST [981-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
A manual run of vacuum analyze roughly halved the use of disk space under /var/lib/postgresql/9.6/main/base/ ...
I've found several web pages talking about autovacuum tuning, but I'm wondering if it wouldn't make sense to disable autovacuum and run a vacuum analyze from a cron job.
Is there a best practice/recommendation for this kind of situation?
And maybe ask the perfsonar project to clean up their code in the long run ;}
locking postgresql-9.6 autovacuum
asked 1 min ago
tinktink
11615
We're running perfsonar on a group of our servers, and while doing some maintenance work found that we
- get giant logfiles under
/var/log/postgresql
- table bloat on the database of the perfsonar scheduler
I assume the toolkit is using table locking when it does ANYTHING on the database, and always cancels the autovacuum run:
2019-04-07 06:33:43 NZST [471-1] ERROR: canceling autovacuum task
2019-04-07 06:33:43 NZST [471-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
2019-04-07 06:34:33 NZST [981-1] ERROR: canceling autovacuum task
2019-04-07 06:34:33 NZST [981-2] CONTEXT: automatic vacuum of table "pscheduler.public.run"
A manual run of vacuum analyze roughly halved the use of disk space under /var/lib/postgresql/9.6/main/base/ ...
I've found several web pages talking about autovacuum tuning, but I'm wondering if it wouldn't make sense to disable autovacuum and run a vacuum analyze from a cron job.
Is there a best practice/recommendation for this kind of situation?
And maybe ask the perfsonar project to clean up their code in the long run ;}
locking postgresql-9.6 autovacuum
locking postgresql-9.6 autovacuum
asked 1 min ago
tinktink
11615
asked 1 min ago
tinktink
11615
asked 1 min ago
tinktink
11615
asked 1 min ago
tinktink
11615
asked 1 min ago
tinktink
11615
11615
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234379%2fpostgres-9-6-6-on-ubuntu-16-04-lots-of-errors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234379%2fpostgres-9-6-6-on-ubuntu-16-04-lots-of-errors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
