| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "daidewei(at)highgo(dot)com" <daidewei(at)highgo(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: a plpgsql bug |
| Date: | 2023-09-19 15:24:25 |
| Message-ID: | CAKFQuwZQnBBDPYq=kj++eh0X_K5eE_+K9yLWBn5vO7K1ysYcNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Sep 18, 2023 at 11:46 PM daidewei(at)highgo(dot)com <daidewei(at)highgo(dot)com>
wrote:
> I found a problem in plpgsql. When there is a large loop in plpgsql,
> it is found that the change of search_path will cause memory exhaustion and
> thus disconnect the connection.
>
It is impossible to prevent queries from exhausting memory so the fact that
this one does isn't an indication of a bug on its own. I'm having trouble
imagining a reasonable use case for this pattern of changing search_path
frequently in a loop within a single execution of a function. That said,
I'm not in a position to judge how easy or difficult an improvement in this
area may be.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-19 16:12:11 | Re: a plpgsql bug |
| Previous Message | Robert Haas | 2023-09-19 14:03:12 | Re: [16+] subscription can end up in inconsistent state |