| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug? |
| Date: | 2017-10-08 17:23:59 |
| Message-ID: | CAFj8pRAUEKdfn-_gLz0ng0P+htd7sJ-m9As3PSfd5mQmbrogww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following workaround is working
>
> create view xxxx as select CISLOEXEKUCE, MT.ID_NAJDATSPLT
> from najzalobpr MT, najvzallok A1,
> NAJZALOBST A2, NAJZALOBCE A3 where
> MT.ID_NAJVZALLOK= A1.ID_NAJVZALLOK AND
> A1.ID_NAJZALOBST=A2.ID_NAJZALOBST AND
> A2.ID_NAJZALOBCE= A3.ID_NAJZALOBCE;
>
>
> and function should be changed to
>
> BEGIN
> BEGIN
> select CISLOEXEKUCE INTO STRICT mADRA
> from xxxx
> WHERE id_najdatsplt = mID_najdatsplt LIMIT 1;
> EXCEPTION
> WHEN OTHERS THEN
> mADRA := NULL;
> END;
>
>
>
> Result:=mADRA;
> return(Result);
> end;
>
> So this issue is really related to tupleDesc management
>
I found a bug in this workaround. It doesn't work
>
>
>> Pavel
>>
>>
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-10-08 17:29:06 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Pavel Stehule | 2017-10-08 17:10:32 | Re: is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug? |