From: | Yogesh Sharma <yogeshraj95(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Request to confirm which command is use for exclusive operation |
Date: | 2017-03-08 06:21:29 |
Message-ID: | CAEZUwCS-F00Amyf7uScw7e35A2cop=J4fTyU9spXjQ3aHxyMjw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dear David,
I want to apply explicitly lock mechanism once inset operation is in
progress then REINDEX will wait.
And vice versa.
So, please let me know this type of handling is possible.
Regrds,
Yogesh
On Wednesday, March 8, 2017, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tuesday, March 7, 2017, Yogesh Sharma <yogeshraj95(at)gmail(dot)com
> <javascript:_e(%7B%7D,'cvml','yogeshraj95(at)gmail(dot)com');>> wrote:
>
>> Dear all,
>>
>> Thanks for your support.
>>
>> I need to perfrom INSERT and REINDEX operation exclusively.
>> For example:
>> If REINDEX operation is in progress then INSERT operation will wait and
>> vice versa.
>>
>> Please let me know if any approach is available.
>>
>>
> The docs describe REINDEX locking mechanics.
>
> https://www.postgresql.org/docs/current/static/sql-reindex.html
>
> That a reindex blocks writes implies the reverse, any writes in progress
> will prevent the reindex from starting.
>
> David J.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2017-03-08 06:55:51 | Re: Request to confirm which command is use for exclusive operation |
Previous Message | David G. Johnston | 2017-03-08 06:03:12 | Re: Request to confirm which command is use for exclusive operation |