Re: BUG #18047: ODBC to PG long transaction causes PANIC

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: justin tocci <justin(at)tocci(dot)org>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #18047: ODBC to PG long transaction causes PANIC
Date: 2023-08-03 23:31:37
Message-ID: CA+hUKG+fj0uupw37y3JN6EJRCiDO5Z4i=bx962u--qJ14eUohg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 3, 2023 at 5:08 PM justin tocci <justin(at)tocci(dot)org> wrote:
> found it! had to set security.bsd.hardlink_check_gid=0 to give postgres the ability to create hard links.

I didn't look closely but it's surprising to me that we didn't log
that link() failed in 15, or cope with it better, or that the gids
didn't match in the first place. But anyway, for the record, this
link() usage is removed in 16 (now in beta).

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=dac1ff3

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-08-04 05:22:29 BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
Previous Message Nathan Bossart 2023-08-03 23:28:41 Re: search_path not recomputed when role name changes