From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "lyes(dot)amd(at)gmail(dot)com" <lyes(dot)amd(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14941: Vacuum crashes |
Date: | 2017-12-01 21:03:59 |
Message-ID: | CA+TgmoY3Azn-6cuuuV7KSJ=eFErJiVpyzUXEQF6J32aCzLLkHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Fri, Dec 1, 2017 at 1:53 PM, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
> There is already an internal flag called VACOPT_NOWAIT that gives
> autovacuum this ability in certain cases (introduced in the aforementioned
> commit), and I recently brought up this potential use-case as
> justification for a patch [0]. I'd be happy to submit a patch for
> providing VACOPT_NOWAIT to users if others think it's something we should
> do.
Seems entirely reasonable to me, provided that we only update the
extensible-options syntax:
VACUUM [ ( option [, ...] ) ] [ table_and_columns [, ...] ]
I don't want to add any more options to the older syntax:
VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ table_and_columns [, ...] ]
I am slightly confused as to how we got on to this topic since the
subject is "Vacuum crashes", but perhaps Lyes was simply speaking
imprecisely.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2017-12-01 21:16:30 | Re: BUG #14941: Vacuum crashes |
Previous Message | Bossart, Nathan | 2017-12-01 18:53:03 | Re: BUG #14941: Vacuum crashes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2017-12-01 21:05:05 | Re: [HACKERS] Additional logging for VACUUM and ANALYZE |
Previous Message | Tomas Vondra | 2017-12-01 20:47:43 | Re: [HACKERS] Custom compression methods |