| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Philip Semanchuk <philip(at)americanefficient(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Avoid excessive inlining? |
| Date: | 2021-01-03 05:57:50 |
| Message-ID: | CAFj8pRBZEXVYyhLDsmXpB9ywvdO3Bo3aEYq=cz1BB14tX+DfEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
so 2. 1. 2021 v 21:02 odesílatel Joel Jacobson <joel(at)compiler(dot)org> napsal:
> 13.1
>
ok there is plpgsql most fast
you can check if there are not some hidden implicit casting in your code.
Regards
Pavel
> On Sat, Jan 2, 2021, at 20:37, Pavel Stehule wrote:
>
> Hi
>
> so 2. 1. 2021 v 20:07 odesílatel Joel Jacobson <joel(at)compiler(dot)org> napsal:
>
>
> I found yet another trick, which actually seems to be slightly faster than
> the plpgsql version.
>
>
> What version of Postgres do you use?
>
> plpgsql in Postgres 13 is significantly faster than on older versions
>
> Regards
>
> Pavel
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Meng Qingzhong | 2021-01-03 12:05:01 | Why not report ERROR when "concurrent insert in progress within table"? |
| Previous Message | Joel Jacobson | 2021-01-02 20:02:38 | Re: Avoid excessive inlining? |