Greetings,
* Meera Nair (mn...@commvault.com) wrote:
> We are following
> https://www.postgresql.org/docs/14/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
> Making An Exclusive Low-Level Backup.
Exclusive backups have been removed, so you really don't want to be
depending on it.
>
"26.3.3.2. Making An Exclusive Low-Level Backup
Note
The exclusive backup method is deprecated and should be avoided. Prior
toPostgreSQL9.6, this was the only low-level method available, but it is now
recommended that all users upgrade their scripts to use non-exclusive backups."
On Tue, Aug 8, 2023 at 5:49 PM Marc Millas wrote:
> also,
> checkpoint setup are all default values
>
> you may try to
> checkpoint_completion_target = 0.9
> checkpoint_timeout = 15min
> max_wal_size = 5GB
>
> and, as said in the previous mail, check the checkpoint logs
>
> Also, all vacuum and
also,
checkpoint setup are all default values
you may try to
checkpoint_completion_target = 0.9
checkpoint_timeout = 15min
max_wal_size = 5GB
and, as said in the previous mail, check the checkpoint logs
Also, all vacuum and autovacuum values are defaults
so, as autovacuum_work_mem = -1
the
Hello,
in the postgresql.conf joined, 2 things (at least) look strange:
1) the values for background writer are the default values, fit for a
server with a limited writes throughput.
you may want to increase those, like:
bgwriter_delay = 50ms
bgwriter_lru_maxpages = 400
bgwriter_lru_multiplier =
On Mon, Aug 7, 2023 at 5:47 PM Amn Ojee Uw wrote:
> Thanks Negora.
>
> Makes sense, I will check it out.
>
> On 8/7/23 1:48 a.m., negora wrote:
>
> Hi:
>
> Although the "postgres" user owns the "data" directory, Has he access to
> the whole branch of directories? Maybe the problem is that he
Hi Team,
We are following
https://www.postgresql.org/docs/14/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
Making An Exclusive Low-Level Backup.
After restoring, we see the server fails to start with below error:
PostgreSQL server log:
2023-08-04 16:47:47.227 IST [40582] LOG: starting
