Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled.
| От | Adrian Klaver |
|---|---|
| Тема | Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled. |
| Дата | |
| Msg-id | 5718E0DA.7050703@aklaver.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL:ALTER TABLE command hangs forever when DB partitioning is enabled. ("Venkatesan, Sekhar" <sekhar.venkatesan@emc.com>) |
| Ответы |
Re: Re: PostgreSQL:ALTER TABLE command hangs forever when DB
partitioning is enabled.
|
| Список | 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.klaver@aklaver.com
В списке pgsql-sql по дате отправления: