Re: hung backends stuck in spinlock heavy endless loop

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hung backends stuck in spinlock heavy endless loop
Date: 2015-01-14 01:24:03
Message-ID: CAM3SWZRuSeCPfDk3qdCqhuFT8JNFnWC_s64yv9nqS_js3cFbhQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 13, 2015 at 3:54 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> Some more information what's happening:
> This is a ghetto logical replication engine that migrates data from
> sql sever to postgres, consolidating a sharded database into a single
> set of tables (of which there are only two). There is only one index
> on the destination table, and it's composite int,int in both cases.

Does the logical replication engine perform dynamic DDL at all? Does
it dynamically add columns to the table that everything is being
consolidated to?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-01-14 01:25:43 Re: EXEC_BACKEND + logging_collector=on is broken
Previous Message Tom Lane 2015-01-14 01:16:33 Re: OOM on EXPLAIN with lots of nodes