Re: plpgsql function startup-time improvements

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: plpgsql function startup-time improvements
Date: 2018-01-25 18:58:03
Message-ID: CAFj8pRAnfEkoJYUnUD_ZNpnDSV8tdLpQk-0rT5_5Z-Q0ZqH7kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

2018-01-25 0:16 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > please, can you rebase all three patches necessary for patching?
>
> Done. These now need to be applied over
> https://www.postgresql.org/message-id/833.1516834367@sss.pgh.pa.us

Thank you

I checked it

1. there are no problem with patching
2. all tests passed
3. I can confirm so some best case speedup is about 15-20%. Worst case is
hard to test - but these changes should not be slower than current master.
4. faster-plpgsql-datum-setup-2.patch is simple patch with few lines of new
code
5. plpgsql-promises-2.patch is little bit more complex, but still it is
simple
6. the code is well formatted and well commented
7. there are not new test and code, what is not problem - these patches
doesn't add any new feature

I'll mark these patches as ready for commiter

Regards

Pavel

>
>
> regards, tom lane
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-01-25 19:09:08 Re: Possible performance regression with pg_dump of a large number of relations
Previous Message Daniel Gustafsson 2018-01-25 17:28:49 Re: CONSTANT/NOT NULL/initializer properties for plpgsql record variables