Re: Vacuum o/p with (full 1, parallel 0) option throwing an error - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
Date
Msg-id CAA4eK1+o5V9_mGyLAcFvkFA0ZMjzwXk8JM89xfFSwjaVmO97zA@mail.gmail.com
Whole thread Raw
In response to Re: Vacuum o/p with (full 1, parallel 0) option throwing an error  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: Vacuum o/p with (full 1, parallel 0) option throwing an error  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
List pgsql-hackers
On Fri, Apr 10, 2020 at 7:05 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
>
>
> No problem.  I think I was trying to make my text similar to that from
> 14a4f6f37.
>
> I realized that I didn't sq!uash my last patch, so it didn't include the
> functional change (which is maybe what Robert was referring to).
>

I think it is better to add a new test for temporary table which has
less data.  We don't want to increase test timings to test the
combination of options.  I changed that in the attached patch.  I will
commit this tomorrow unless you or anyone else has any more comments.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: weird hash plan cost, starting with pg10
Next
From: Amit Kapila
Date:
Subject: Re: doc review for parallel vacuum