| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Yogesh Sharma <yogeshraj95(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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:57:28 |
| Message-ID: | CAOR=d=1eoibsOCOcn738jO--c2thtcoF87EhEC_BYJP=XhVwJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 7, 2017 at 11:55 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Tue, Mar 7, 2017 at 11:21 PM, Yogesh Sharma <yogeshraj95(at)gmail(dot)com> wrote:
>> 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
>
> Create two roles grant / revoke permissions as needed. maybe
> pg_stat_activity for locks etc
Also you could have a table with a simple token in it etc. active
process gets token, all other processes wait on it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vinny | 2017-03-08 07:54:35 | Re: Postgres, apps, special characters and UTF-8 encoding |
| Previous Message | Scott Marlowe | 2017-03-08 06:55:51 | Re: Request to confirm which command is use for exclusive operation |