On 17/05/16 00:54, Scott Moynes wrote:
> wal_keep_segments is set to 32.
>
> Here is the replication slot:
>
> slot_name|
> n6lbb2vmohwuxoyk_00018732_f58b5354_79ad_4e6e_b18b_47acb1d7ce1f
> plugin | test_decoding
> slot_type| logical
> datoid | 18732
>
wal_keep_segments is set to 32.
Here is the replication slot:
slot_name|
n6lbb2vmohwuxoyk_00018732_f58b5354_79ad_4e6e_b18b_47acb1d7ce1f
plugin | test_decoding
slot_type| logical
datoid | 18732
database | omitted
active | f
xmin |
On 05/16/2016 03:33 PM, Scott Moynes wrote:
I have a PostgreSQL server that is not recycling WAL files. Log files
are continually created and no old log files are ever removed.
Running PostgreSQL v 9.4.8 with archive settings:
archive_mode = on
archive_command = /bin/true
Checkpoint
Scott Moynes wrote:
> I have a PostgreSQL server that is not recycling WAL files. Log files are
> continually created and no old log files are ever removed.
>
> Running PostgreSQL v 9.4.8 with archive settings:
>
> archive_mode = on
> archive_command = /bin/true
>
> Checkpoint logging
I have a PostgreSQL server that is not recycling WAL files. Log files are
continually created and no old log files are ever removed.
Running PostgreSQL v 9.4.8 with archive settings:
archive_mode = on
archive_command = /bin/true
Checkpoint logging is enabled and does not record any logs