Re: Comment in portal.h

From: Andy Fan <zhihuifan1213(at)163(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Comment in portal.h
Date: 2024-07-30 23:55:39
Message-ID: 87plqusadg.fsf@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> writes:

> Hi,
>
> I noticed $SUBJECT while working on something else:
>
> /*
> * Where we store tuples for a held cursor or a PORTAL_ONE_RETURNING or
> * PORTAL_UTIL_SELECT query. (A cursor held past the end of its
> * transaction no longer has any active executor state.)
> */
> Tuplestorestate *holdStore; /* store for holdable cursors */
> MemoryContext holdContext; /* memory containing holdStore */
>
> We do that for PORTAL_ONE_MOD_WITH as well, so the comment should be
> "Where we store tuples for a held cursor or a PORTAL_ONE_RETURNING,
> PORTAL_ONE_MOD_WITH, or PORTAL_UTIL_SELECT query.". Attached is a
> patch for that.

Patch looks good to me.

All the codes of PortalRun & FillPortalStore & PortalRunSelect are
consistent with this idea.

--
Best Regards
Andy Fan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-07-31 00:21:22 Re: Do we still need parent column in pg_backend_memory_context?
Previous Message Noah Misch 2024-07-30 23:54:55 Re: race condition when writing pg_control