Subject: Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB
 partitioning is enabled.
To: "Venkatesan, Sekhar" <sekhar.venkatesan@emc.com>,
 "pgsql-sql@postgresql.org" <pgsql-sql@postgresql.org>
References: <F84DE43FDACD4C45AA84E2DA016FAE2F1C6A75A5@MX105CL01.corp.emc.com>
Cc: "Choudhuri, Saurav" <saurav.choudhuri@emc.com>,
 "Rao, Raghavendra" <raghavendra.rao@emc.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
Message-ID: <5718E0DA.7050703@aklaver.com>
Date: Thu, 21 Apr 2016 07:16:58 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <F84DE43FDACD4C45AA84E2DA016FAE2F1C6A75A5@MX105CL01.corp.emc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

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.klaver@aklaver.com


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql