Re: CREATE LIKE INCLUDING COMMENTS and STORAGES

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE LIKE INCLUDING COMMENTS and STORAGES
Date: 2009-10-12 19:41:07
Message-ID: 4AD38653.6060209@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Itagaki Takahiro wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
>> I'm wondering why we are not
>> copying comments on cloned indexes. I realize that might involve a bit
>> more code, but I think I'd feel happier if we cloned all the comments we
>> reasonably could from the outset. Is it really that hard to do?
>>
>
> I found it is not so difficult as I expected; patch attached. Now it copies
> comments on indexes and columns of the indexes on INCLUDING COMMENTS.
> Regression test and documentation are also adjusted. Please review around
> chooseIndexName() and uses of it.
>
> The codes becomes a bit complex and might be ugly because we will have some
> duplicated codes; "pg_expression_%d" hacks and uses of ChooseRelationName()
> are spread into index.c, indexcmds.c and parse_utilcmd.c.
>
>
>

I don't think that's a terrible tragedy - you haven't copied huge swags
of code. Committed with slight adjustments for bitrot etc.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2009-10-12 20:12:51 Re: GRANT ON ALL IN schema
Previous Message Tom Lane 2009-10-12 19:29:04 Re: EvalPlanQual seems a tad broken