| From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
|---|---|
| To: | jacktby jacktby <jacktby(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Buffer ReadMe Confuse |
| Date: | 2023-09-14 23:26:47 |
| Message-ID: | CAKU4AWo-W5=ngB8mBvHwXxQLL7L522TzRvcXc7S2iJ2HmZyx6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 15, 2023 at 4:08 AM jacktby jacktby <jacktby(at)gmail(dot)com> wrote:
> In buffer README, I see “Pins may not be held across transaction
> boundaries, however.” I think for different transactions, they can pin the
> same buffer page, why not? For concurrent read transactions, they could
> read the one and the same buffer page.
>
>
You are right that different transactions can pin the same buffer,
but that does not conflict with what the README says, which is talking
about once the transaction is completed, all the Pins are removed.
--
Best Regards
Andy Fan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2023-09-14 23:28:26 | Re: Is it possible to change wal_level online |
| Previous Message | Thomas Munro | 2023-09-14 23:04:23 | Re: Cygwin cleanup |