wstrzalka <[EMAIL PROTECTED]> writes:
> archive_timeout is used for WAL shipping to standby server in my case
> (are there any other reasons?), but WAL is switched by the timeout
> even if there are no changes on the server.
This is intentional. Some people consider the arrival of a new WAL file
I've just realized that I can call pg_switch_xlog() from cron or
pgAgent instead of using archive_timeout, but the question is still
open. Doing it internally in PG would be much more elegant.
Thanks
Wojtek Strzalka
--
Sent via
I have a question if it is possible that having archive_timeout set up
it will behave like pg_switch_xlog() in the term of non creating new
WAL when there are no changes in the database.
archive_timeout is used for WAL shipping to standby server in my case
(are there any other reasons?), but WAL i
