Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled.

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: "Venkatesan, Sekhar" <sekhar(dot)venkatesan(at)emc(dot)com>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>
Cc: "Choudhuri, Saurav" <saurav(dot)choudhuri(at)emc(dot)com>, "Rao, Raghavendra" <raghavendra(dot)rao(at)emc(dot)com>
Subject: Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled.
Date: 2016-04-21 14:16:58
Message-ID: 5718E0DA.7050703@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On 04/21/2016 03:23 AM, Venkatesan, Sekhar wrote:
> For DROP_INDEX case, adding the lock_timeout setting to few seconds
> helps in clearing the DB locks and the drop index operation to complete.
>
> For ALTER table hang issue, none of the DB timeout settings are helping.
>
> Need your assistance to identify if there is any known issue when data
> partitioning is enabled in PostgreSQL DB.

You have shown the error, but it would be helpful to know what the setup is:

What are the tables involved in the partitioning scheme?

How is the partitioning been done?

How are the statements being sent to server?

In particular I am seeing a BEGIN on the DDL statements, is that coming
from you or the client software?

>
> Thanks,
> Sekhar

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Michael Moore 2016-04-22 22:50:14 How to get pgsql to echo commands in a command file
Previous Message Venkatesan, Sekhar 2016-04-21 10:23:14 Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled.