| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: archiving question |
| Date: | 2019-12-04 17:56:18 |
| Message-ID: | 20191204175618.GH6962@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greetings,
* Zwettler Markus (OIZ) (Markus(dot)Zwettler(at)zuerich(dot)ch) wrote:
> When there is a Postgres archiver stuck because of filled pg_xlog and archive directories...
>
> ... and the pg_xlog directory had been filled with dozens of GBs of xlogs...
>
> ...it takes ages until the archive_command had moved all xlogs from the pg_xlog directory to the archive directory afterwards...
>
> ... and you get crazy if you have a 8GB archive directory while the pg_xlog directory had been pumped up to 100GB :(
>
>
> Any idea on this one?
Parallelizing the archive-push operation can be quite helpful to address
this.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hu, Patricia | 2019-12-04 20:48:38 | what causes xact_rollback for a database in pg_stat_database to increment? |
| Previous Message | Zwettler Markus (OIZ) | 2019-12-04 16:49:13 | archiving question |