| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Locks on unlogged tables are locked?! |
| Date: | 2023-11-21 20:18:44 |
| Message-ID: | ZV0QpFDBHP2ylj0-@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 21, 2023 at 01:16:19PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Uh, was this ever addressed? I don't see the patch applied or the code
> > in this area modified.
>
> This patch as-is would surely be disastrous: having LockAcquire
> try to open the relcache entry for the thing we're trying to lock
> is going to be circular in at least some cases. I'm not convinced
> that there's a problem worth solving here, but if there is, it'd
> have to be done in some other way.
Thank you, and Robert, for the feedback.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-21 20:33:02 | Re: vacuum_cost_limit doc description patch |
| Previous Message | David Steele | 2023-11-21 20:08:35 | Re: Add recovery to pg_control and remove backup_label |