Postgresql - limit size of logged message
I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).
I have configured PostgreSQL to keep track of low performing queries by setting:
log_min_duration_statement = 200
Due to this my PostgreSQL log is filled with huge mess, something like:
2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0
obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...
This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.
- Is there any way to "cut" the string in the detail to some maximal size?
- Or to limit the size of the log file?
postgresql-9.5 log
edited 6 mins ago
hot2use
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
add a comment |
I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).
I have configured PostgreSQL to keep track of low performing queries by setting:
log_min_duration_statement = 200
Due to this my PostgreSQL log is filled with huge mess, something like:
2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0
obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...
This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.
- Is there any way to "cut" the string in the detail to some maximal size?
- Or to limit the size of the log file?
postgresql-9.5 log
edited 6 mins ago
hot2use
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
add a comment |
I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).
I have configured PostgreSQL to keep track of low performing queries by setting:
log_min_duration_statement = 200
Due to this my PostgreSQL log is filled with huge mess, something like:
2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0
obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...
This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.
- Is there any way to "cut" the string in the detail to some maximal size?
- Or to limit the size of the log file?
postgresql-9.5 log
edited 6 mins ago
hot2use
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
I'm trying to overcome a problem with unreadable PostgreSQL log. There is a database that contains (unfortunately) files in column with datatype bytea (bad application design, lot of time to rework to mongo etc.).
I have configured PostgreSQL to keep track of low performing queries by setting:
log_min_duration_statement = 200
Due to this my PostgreSQL log is filled with huge mess, something like:
2018-07-01 09:03:31 CEST DETAIL: parameters: $1 = '38007670', $2 =
'9772671', $3 = '%PDF-1.515%34234331732315121 0
obj15<</Metadata 2 0 R/OCProperties<</D<</OFF[8 0 R]/ON[9 0 R 10 0 R
11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R] ...
This can go on well over thousands of lines in the log file and it just makes the whole thing unusable.
- Is there any way to "cut" the string in the detail to some maximal size?
- Or to limit the size of the log file?
postgresql-9.5 log
postgresql-9.5 log
edited 6 mins ago
hot2use
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
edited 6 mins ago
hot2use
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
edited 6 mins ago
hot2use
8,35752055
edited 6 mins ago
hot2use
8,35752055
edited 6 mins ago
hot2use
8,35752055
8,35752055
asked Jul 2 '18 at 7:21
krszpkrszp
11
asked Jul 2 '18 at 7:21
krszpkrszp
11
asked Jul 2 '18 at 7:21
krszpkrszp
11
11
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%2f211103%2fpostgresql-limit-size-of-logged-message%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%2f211103%2fpostgresql-limit-size-of-logged-message%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
