From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Comment in portal.h |
Date: | 2024-07-30 10:39:27 |
Message-ID: | CAPmGK14HVYBZYZtHabjeCd-e31VT=wx6rQNq8QfehywLcpZ2Hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Best regards,
Etsuro Fujita
Attachment | Content-Type | Size |
---|---|---|
update-comment.patch | application/octet-stream | 844 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2024-07-30 10:58:17 | Re: Slow catchup of 2PC (twophase) transactions on replica in LR |
Previous Message | Peter Eisentraut | 2024-07-30 10:35:40 | Re: speed up a logical replica setup |