Re: Avoid deadlocks on alter table

From: Christian Castelli <voodoo81people(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Avoid deadlocks on alter table
Date: 2016-07-06 13:45:06
Message-ID: CAN7CK_xs7wgdufcKe-fRHAqLKE5U0U7dd5gqBTx2Y0+2K31TrA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
by splitting FK contraints, once failed on fk_plan creation while the
second time failed on rebuilding public views. I've done a PLPGSQL function
that cycles through all schemata and builds views with lots of UNION to
join the result. Obviously there are other processes which use these global
views so how can I update these global views without interfering with other
processes?
Should I avoid using these views and build by myself the queries with code?
Is there another better approach for finding results with this type of
architecture?
Thanks.

2016-07-06 9:43 GMT+02:00 Christian Castelli <voodoo81people(at)gmail(dot)com>:

>
> 2016-07-05 16:01 GMT+02:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
>
>>
>> Does the server log have the details, per above?
>
>
> No, it copies just the schema from base_template with a CREATE TABLE x AS
> base_template.x WITH NO DATA.
>
> 2016-07-05 17:24 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
>> I think it'd likely be enough to add the FKs one at a time, rather
>> than all in one transaction.
>>
>
> Ok I'll try first to do this.
> Thanks.
>
>
> --
>
> *Christian Castelliskype: christrack*
>

--

*Christian Castelliskype: christrack*

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Olarte 2016-07-06 14:30:17 Re: pg_dump fundenental question
Previous Message Rémi Cura 2016-07-06 13:42:46 Re: Update statement results in Out of memory