From: | "Nick Renders" <postgres(at)arcict(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres 12.1 : UPPER() in WHERE clause restarts server |
Date: | 2020-02-11 11:32:05 |
Message-ID: | A2345E27-7BB3-411B-B4D1-1572BBA4FC03@arcict.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Thomas,
We are setting up a new test environment with 12.1.
Once it is running, I'll try out those commands and get back with the
results.
Thanks,
Nick Renders
On 11 Feb 2020, at 2:51, Thomas Munro wrote:
> On Mon, Feb 10, 2020 at 4:35 AM Marc <postgres(at)arcict(dot)com> wrote:
>> We will keep the 12.1 in place so that we can run additional tests to
>> assist to pin-point the issue.
>>
>> Feel free to ask but allow us to recover from these hectic days ;-)
>
> Here's how to get a stack so we can see what it was doing, assuming
> you have the Apple developer tools installed:
>
> 1. Find the PID of the backend you're connected to with SELECT
> pg_backend_pid().
> 2. "lldb -p PID" from a shell to attach to the process, then "cont"
> to let it continue running.
> 3. Run the query in that backend and wait for the SIGKILL.
> 4. In the lldb session, type "bt".
>
> It'll only make sense if your PostgreSQL build has debug symbols, but
> let's see.
From | Date | Subject | |
---|---|---|---|
Next Message | Vikram Sah | 2020-02-11 11:56:30 | Re: Function not imported in Entity Framework |
Previous Message | Thomas Munro | 2020-02-11 01:51:17 | Re: Postgres 12.1 : UPPER() in WHERE clause restarts server |