Re: Write Ahead Logging for Hash Indexes

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Write Ahead Logging for Hash Indexes
Date: 2016-08-24 04:52:27
Message-ID: ab461bc0-aa88-f78d-b380-8320d1943b7f@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 24/08/16 16:33, Amit Kapila wrote:
> On Wed, Aug 24, 2016 at 9:53 AM, Mark Kirkwood
> <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
>> On 24/08/16 15:36, Amit Kapila wrote:
>>> On Wed, Aug 24, 2016 at 8:54 AM, Mark Kirkwood
>>> <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
>>> Can you get the call stacks?
>>>
>> For every stuck backend? (just double checking)...
> Yeah.
>

Cool,

I managed to reproduce with a reduced workload of 4 backends, then
noticed that the traces for 3 of 'em were all the same. So I've attached
the 2 unique ones, plus noted what pg_stat_activity thought the wait
event was, in case that is useful.

Cheers

Mark

Attachment Content-Type Size
bt.out text/plain 14.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-08-24 04:56:16 Re: patch: function xmltable
Previous Message Michael Paquier 2016-08-24 04:50:43 Re: LSN as a recovery target