| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | NikhilS <nikkhils(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Trevor Hardcastle <chizu(at)spicious(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
| Date: | 2007-07-16 10:08:52 |
| Message-ID: | 1184580532.29879.3.camel@goldbach |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2007-16-07 at 14:28 +0530, NikhilS wrote:
> Guess you want to use "src_options" here to be uniform with usages
> elsewhere that you have replaced.
Thanks, good catch.
> You suppose "src_options" is much more readable than "inhreloptions"
> or "inh_idxoptions"? Your call :).
Yeah, I'm not necessarily sure that it is. "inhreloptions" made me think
of table inheritance, whereas LIKE in general is more of a "source" =>
"target" copying operation. But I'm not convinced about src_options,
either ... suggestions/comments welcome.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | NikhilS | 2007-07-16 10:20:09 | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
| Previous Message | NikhilS | 2007-07-16 08:58:32 | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | NikhilS | 2007-07-16 10:20:09 | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
| Previous Message | Affan Salman | 2007-07-16 09:20:56 | Re: Deferred RI trigger for non-key UPDATEs and subxacts |