On Jan 24, 2008, at 6:09 AM, Roberto Scattini wrote:
> On Jan 23, 2008 11:07 PM, Greg Smith <gsmith@gregsmith.com> wrote:
>> On Wed, 23 Jan 2008, Roberto Scattini wrote:
>>
>>> the problem that im having is that i have A LOT of
>>> archive files on pg_xlog dir, and thats because the archive_command
>>> keeps failing (the standby server had filled his disk with archives
>>> received but not proccesed), so now, i dont know how i can remove
>>> those files and start again...
>>
>> Under normal operation the checkpoint process will look at the
>> number of
>> already created archive files, keep around up to
>> (2*checkpoint_segments+1)
>> of them for future use, and delete the rest of them. You never
>> delete
>> them yourself, the server will take care of that automatically
>> once it
>> gets to where it makes that decision. If you set
>> checkpoint_segments to
>> some very high number they can end up taking many GB worth of
>> storage,
>> increasing that parameter has at least two costs associated with
>> it (the
>> other being a longer recovery time).
>>
>
> i had commented archive_command in the main server but i only made a
> reload. now i made a restart and almost all files in $DATA/pg_xlog/
> dir are gone, and the server works properly :D
>
> question: all the parameters in postgresql.conf need a restart to
> take effect?
>
> thanks all for your help.
Ah, yes, that's a gotcha with the archive_command, at least I know it
was a gotme at one point :) To disable archiving, set
archive_command="", commenting it out won't change it. The only
config paramaters that require a restart to take effect are those
that are specifically noted as such in the manual section on server
configuration. However, commenting a config is not necessarily
equivalent to disabling something.
Erik Jones
DBA | Emma®
erik@myemma.com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com