Re: "no unpinned buffers available" ? why? (hstore and plperl involved)
От | hubert depesz lubaczewski |
---|---|
Тема | Re: "no unpinned buffers available" ? why? (hstore and plperl involved) |
Дата | |
Msg-id | 9e4684ce0701040021l13ee4cfdv743ca1a087414467@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: "no unpinned buffers available" ? why? (hstore and (Richard Huxton <dev@archonet.com>) |
Ответы |
Re: "no unpinned buffers available" ? why? (hstore and
|
Список | pgsql-general |
On 1/3/07, Richard Huxton <dev@archonet.com> wrote:
this information is stored there, yet i have no clue on how you would like to make it with standard sql statements? for every "advert" there are about 20-30 "custom fields" (in one record in advert_custom_fields). to do it your way i would need to make approximatelly 30 (numer of custom field) times 300000 (number of adverts) queries. that would be way slower and definitelly not automatic.
best regards,
depesz
--
http://www.depesz.com/ - nowy, lepszy depesz
hubert depesz lubaczewski wrote:
> On 1/3/07, Richard Huxton <dev@archonet.com> wrote:
>>
>> If you do that separately at the start of the process, (one query per
>> custom column in the old table) then it becomes straightforward.
>>
>
> no, because meaning of "col1" in advert_custom_fields is different for each
> record.
> for one record it's codename might be "email" for another record it
> might be
> "engine size".
And is that not what's stored in "v_category_custom_fields"? So you can
do the transformation and get (advert_id=1, codename='col1',
value='vvv') then use v_category_custom_fields to update the 'col1' part.
this information is stored there, yet i have no clue on how you would like to make it with standard sql statements? for every "advert" there are about 20-30 "custom fields" (in one record in advert_custom_fields). to do it your way i would need to make approximatelly 30 (numer of custom field) times 300000 (number of adverts) queries. that would be way slower and definitelly not automatic.
best regards,
depesz
--
http://www.depesz.com/ - nowy, lepszy depesz
В списке pgsql-general по дате отправления: