Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
Date
Msg-id 92B0A7CD-B1A8-4EB6-A30F-2E3E1A206A24@amazon.com
Whole thread Raw
In response to Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
List pgsql-hackers
On 9/8/17, 1:27 AM, "Michael Paquier" <michael.paquier@gmail.com> wrote:
> Thanks. This looks now correct to me. Except that:
> +           ereport(ERROR,
> +               (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> +                errmsg("column lists cannot have duplicate entries"),
> +                errhint("the column list specified for relation
> \"%s\" contains duplicates",
> +                   relation->relation->relname)));
> This should use ERRCODE_DUPLICATE_COLUMN.

Absolutely.  This is fixed in v3.

Nathan


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] code cleanup empty string initializations
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] The case for removing replacement selection sort