| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: vacuumdb error |
| Date: | 2009-10-16 13:07:18 |
| Message-ID: | bddc86150910160607k54be50b5od476e2e455f0a74c@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2009/10/16 Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>:
> Thom Brown wrote:
>> Thanks Heikki. You probably already know, but remember to prevent it
>> using FREEZE at all for 8.5+ as according to the documentation it's
>> being deprecated.
>
> It's been documented as deprecated since 8.2, in favor of the
> vacuum_freeze_max_age option. However, it's still widely used in the
> field, and there's no immediate reason to remove it, so I don't think
> we're actually going to remove it in the foreseeable future.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
Sorry, I mean the actual keyword will be removed meaning it would
error if used as an option, although whether it'll be in 8.5 I don't
actually know.
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-16 13:32:20 | Re: vacuumdb error |
| Previous Message | Heikki Linnakangas | 2009-10-16 12:40:24 | Re: vacuumdb error |