| From: | Kirk Wolak <wolakk(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already] |
| Date: | 2024-01-16 01:53:55 |
| Message-ID: | CACLU5mS7phwdcso8TkJrJ_QgH6kwxBA8y3Hvbt8y0b4vN3ZkzQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 15 Jan 2024, at 07:24, Kirk Wolak <wolakk(at)gmail(dot)com> wrote:
>
> > You have a commit [1] that MIGHT fix this.
> > I have a script that recreates the problem, using random data in pg_temp.
> > And a nested cursor.
>
> Running your reproducer script in a tight loop for a fair bit of time on
> the
> v16 HEAD I cannot see any memory growth, so it's plausible that the
> upcoming
> 16.2 will work better in your environment.
>
Okay, I took the latest source off of git (17devel) and got it to work
there in a VM.
It appears this issue is fixed. It must have been related to the issue
originally tagged.
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2024-01-16 01:55:44 | Re: [17] CREATE SUBSCRIPTION ... SERVER |
| Previous Message | Peter Smith | 2024-01-16 01:27:26 | Re: Synchronizing slots from primary to standby |