Re: [COMMITTERS] pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [COMMITTERS] pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY
Date
Msg-id 55ACA793.7080400@iki.fi
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [COMMITTERS] pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 07/18/2015 04:15 PM, Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>> If it's there just to so you can run the regression tests that come
>> with it, it might make sense to just add a "default" case to that
>> switch to handle any unrecognized commands, and perhaps even remove
>> the cases for the currently untested subcommands as it's just dead
>> code.
>
> Well, I would prefer to have an output that says "unrecognized" and then
> add more test cases to the SQL files so that there's not so much dead
> code.  I prefer that to removing the C support code, because then as
> we add extra tests we don't need to modify the C source.

Ok. I added a case for AT_ReAddComment, and also a default-case that 
says "unrecognized".
- Heikki




pgsql-hackers by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace
Next
From: Simon Riggs
Date:
Subject: Re: Support for N synchronous standby servers - take 2