Re: Query regarding deadlock

From: Jan de Visser <jan(at)de-visser(dot)net>
To: Yogesh Sharma <Yogesh1(dot)Sharma(at)nectechnologies(dot)in>, John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Query regarding deadlock
Date: 2016-11-25 02:17:09
Message-ID: 6234d1c4-54e9-e5f3-6ada-7e6d24e864af@de-visser.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2016-11-24 9:06 PM, Yogesh Sharma wrote:

> Dear John,
>
> Thanks for your support.
> I mean to say, the REINDEX calls hourly and insert query executes every minute to update.
> So, it might be race condition that these queries can call at same time.

Why do you need to run REINDEX every hour? That sounds like a stopgap
solution for another problem.
> If there is any solution like we can add some check before REINDEX operation performed.
> If it is possible?

Try to find out why the cron script is there in the first place. Then go
from there - eliminate it, or do it only in down periods.

>
> Regards,
> Yogesh
>
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of John R Pierce
> Sent: Friday, November 25, 2016 10:55 AM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Query regarding deadlock
>
> On 11/24/2016 5:44 PM, Yogesh Sharma wrote:
>> I cannot change calling of REINDEX and insert query sequence because it is execute automatically through some cron script.
> any cron scripts are your own doing, so this statement makes no sense at all.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2016-11-25 02:19:38 Re: Query regarding deadlock
Previous Message Sameer Kumar 2016-11-25 02:14:26 Re: Query regarding deadlock