| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tomas Vondra <tv(at)fuzzy(dot)cz>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Re: hio.c does visibilitymap_pin()/IO while holding buffer lock |
| Date: | 2023-03-25 16:57:17 |
| Message-ID: | 2602455.1679763437@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2023-03-25 14:34:25 +0100, Tomas Vondra wrote:
>> Can't we ensure we actually lock the vm buffer too in ReadBufferBI,
>> before calling ReadBufferExtended? Or am I confused and that's not
>> possible for some reason?
> Note that this is using P_NEW. I.e. we don't know the buffer location yet.
Maybe the relation-extension logic needs to include the ability to get
the relevant vm page?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-25 17:11:17 | Re: Progress report of CREATE INDEX for nested partitioned tables |
| Previous Message | Andres Freund | 2023-03-25 16:39:03 | Re: hio.c does visibilitymap_pin()/IO while holding buffer lock |