On Fri, May 19, 2017 at 10:00 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Michael Paquier <michael.paqu...@gmail.com> writes: >> On Fri, May 19, 2017 at 9:06 AM, Michael Paquier >> <michael.paqu...@gmail.com> wrote: >>> I am fine with an ERROR if a column list is specified without ANALYZE >>> listed in the options. But that should happen as well for the case >>> where only one relation is listed. > >> Perhaps this could be changed for 10? Changing the behavior in >> back-branches looks sensitive to me. > > It would make more sense to me to change it as part of the feature > addition, when/if this patch gets committed. Otherwise, we just break > code that works today and we can't point to any solid benefit.
Fine for me as well. I would suggest to split the patch into two parts to ease review then: - Rework this error handling for one relation. - The main patch. -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers