| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Doc fix for VACUUM FREEZE |
| Date: | 2013-12-20 04:12:31 |
| Message-ID: | CAA4eK1JN8SUBJgiMx3A+n=6z8rGUtHxozocJiCVWrVL1w3+biQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 18, 2013 at 6:46 AM, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> wrote:
>VACUUM FREEZE sets both vacuum_freeze_min_age and vacuum_freeze_table_age to 0, but only the former is documented. This patch notes that the other setting is also affected.
> (now with patch--sorry about that)
Your explanation and patch seems fine to me.
Kindly submit your patch in Open CommitFest
(https://commitfest.postgresql.org/action/commitfest_view?id=21)
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sawada Masahiko | 2013-12-20 05:05:23 | Re: Logging WAL when updating hintbit |
| Previous Message | Peter Geoghegan | 2013-12-20 04:06:29 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |