"Andrus" <[EMAIL PROTECTED]> writes:
> Please confirm that it it not possible to set archive_command parameter to
> unset state from Postgres client.
It works fine for me. Maybe you got bit by that bug you pointed out
yesterday that there must be a newline after a postgresql.conf entry?
> This is a known problem - since pg_reload_conf() will ignore the lines
> with a # (comment), so the old value is kept.
I tried to add a line
archive_command=''
But after pg_reload_conf() postmaster still uses the old value which exists
in its memory.
Please confirm that it it not possible t
"Andrus Moor" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> 1. Make sure that postgres.conf file contains in first line:
>
> archive_command = 'copy "%p" "c:/arhiiv/%f"'
>
> 2. Edit postgres.conf file by adding # before this line
>
> #archive_command = 'copy "%p" "c:/arhiiv/%f"'
"Andrus Moor" <[EMAIL PROTECTED]> writes:
> 1. Make sure that postgres.conf file contains in first line:
> archive_command = 'copy "%p" "c:/arhiiv/%f"'
> 2. Edit postgres.conf file by adding # before this line
> #archive_command = 'copy "%p" "c:/arhiiv/%f"'
The latter is a comment and does not cha
