| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Jessica Sharp <jessica(at)thesharpgeek(dot)com> |
| Cc: | Atul Kumar <akumar14871(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: meaning of (to prevent wraparound) ..?? |
| Date: | 2020-11-26 07:23:19 |
| Message-ID: | X79X50QMv/y0l9iA@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 25, 2020 at 11:10:50PM -0700, Jessica Sharp wrote:
> On Wed, Nov 25, 2020 at 23:09 Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
>> Thanks Jessica. Could help me out by sharing documents that can help me
>> understand “to prevent wraparound “ in simplest way, postgres doc is little
>> bit harder for a newbee like me.
>
> Absolutely. This may be helpful:
> https://youtu.be/bA1SgWn6Gv4
If you have any suggestions on how to improve this part of the docs,
please feel free:
https://www.postgresql.org/docs/devel/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
Note that due to the critical work that such vacuum jobs do, they
cannot be cancelled.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-11-26 17:07:41 | Re: postgres_fdw insert extremely slow |
| Previous Message | Jessica Sharp | 2020-11-26 06:10:50 | Re: meaning of (to prevent wraparound) ..?? |