Re: PATCH: CreateComments: use explicit indexing for ``values''
От | Robert Haas |
---|---|
Тема | Re: PATCH: CreateComments: use explicit indexing for ``values'' |
Дата | |
Msg-id | BANLkTi=iK7ixy=bBTN=okdJuz2PGQyR_Yg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: CreateComments: use explicit indexing for ``values'' (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Tue, Jun 14, 2011 at 10:30 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: >> Excerpts from richhguard-monotone's message of lun jun 13 16:10:17 -0400 2011: >>> Do you have any advice of how to handle the inner loops, such as those initializing ``stakindN''. The entries beforecan be handled just like in this patch, by using the symbolic constants. > >> Based on Tom's comments, I'd submit the patch without that bit, at least >> as a first step. > > He already did no? > > I did think of a possible way to rewrite update_attstats: instead of > > for (k = 0; k < STATISTIC_NUM_SLOTS; k++) > { > values[i++] = ObjectIdGetDatum(stats->staop[k]); /* staopN */ > } > > do > > for (k = 0; k < STATISTIC_NUM_SLOTS; k++) > { > values[Anum_pg_statistic_staop1 - 1 + k] = ObjectIdGetDatum(stats->staop[k]); > } > > etc. However, it's not clear to me whether this is really an > improvement. Opinions? I don't care that much, but IMV that's just gilding the lily. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: