| From: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | AW: archiving question |
| Date: | 2019-12-05 15:04:55 |
| Message-ID: | 200ee00c33104728b9a6b8df8ca90226@zuerich.ch |
| 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
What do you mean hear?
Afaik, Postgres runs the archive_command per log, means log by log by log.
How should we parallelize this?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-12-05 15:05:11 | Re: We have to close the cursor or rollback the transaction in case of failure? |
| Previous Message | Zwettler Markus (OIZ) | 2019-12-05 14:49:28 | AW: secure deletion of archived logs |