parameter "vacuum_defer_cleanup_age"

Started by Tulioabout 14 years ago5 messagesgeneral
Jump to latest
#1Tulio
tulio@informidia.com.br

Attachments:

logoInformidia.jpgimage/jpeg; name=logoInformidia.jpgDownload
#2Fabrízio de Royes Mello
fabriziomello@gmail.com
In reply to: Tulio (#1)
Re: parameter "vacuum_defer_cleanup_age"

2012/1/30 Tulio <tulio@informidia.com.br>

Hi,

I have 2 servers, working with Hot-Standby and Streaming Replication...
and when we executed some query much large returns a message..
"canceling *statement due* to *statement* timeout"
I want know, how can I calculate the better value to
"vacuum_defer_cleanup_age" in my case?

Tell me if you recommend changes in other parameter.

Which the value of the parameter "statement_timeout" ?

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL

Show quoted text

Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello

#3Tulio
tulio@informidia.com.br
In reply to: Fabrízio de Royes Mello (#2)
Re: parameter "vacuum_defer_cleanup_age"

Attachments:

logoInformidia.jpgimage/jpeg; name=logoInformidia.jpgDownload
#4Marti Raudsepp
marti@juffo.org
In reply to: Tulio (#1)
Re: parameter "vacuum_defer_cleanup_age"

On Mon, Jan 30, 2012 at 20:55, Tulio <tulio@informidia.com.br> wrote:

I have 2 servers, working with Hot-Standby and Streaming Replication...
and when we executed some query much large returns a message..
"canceling statement due to statement timeout"
I want know, how can I calculate the better value to "vacuum_defer_cleanup_age" in my case?

This error doesn't happen due to recovery conflict, so
vacuum_defer_cleanup_age doesn't make any difference. The error
happens because the statement_timeout setting is configured somewhere
(maybe per-database or per-user settings). Set it to 0 to disable the
statement timeout.

Regards,
Marti

#5Tulio
tulio@informidia.com.br
In reply to: Marti Raudsepp (#4)
Re: parameter "vacuum_defer_cleanup_age"

<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
Hi Marti,<br>
<br>
The parameter statement_timeout isn't configured..<br>
I'm using the value default.. 0.. <br>
<br>
And this is happening when I'm doing large querys on the slave..<br>
<br>
thanks,<br>
Tulio<br>
<br>
Em 01/02/2012 12:33, Marti Raudsepp escreveu:
<blockquote
cite="mid:CABRT9RC=XoYRx=eHtkAYSxAGesU_hKGAORCzZV1WbqkGfOmYWw@mail.gmail.com"
type="cite">
<pre wrap="">On Mon, Jan 30, 2012 at 20:55, Tulio <a class="moz-txt-link-rfc2396E" href="mailto:tulio@informidia.com.br">&lt;tulio@informidia.com.br&gt;</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have 2 servers, working with Hot-Standby and Streaming Replication...
and when we executed some query much large returns a message..
"canceling statement due to statement timeout"
I want know, how can I calculate the better value to "vacuum_defer_cleanup_age" in my case?
</pre>
</blockquote>
<pre wrap="">
This error doesn't happen due to recovery conflict, so
vacuum_defer_cleanup_age doesn't make any difference. The error
happens because the statement_timeout setting is configured somewhere
(maybe per-database or per-user settings). Set it to 0 to disable the
statement timeout.

Regards,
Marti
</pre>
</blockquote>
</body>
</html>