| From: | Yogesh Sharma <yogeshraj95(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(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 08:30:10 |
| Message-ID: | CAEZUwCRa12VgQZRT73Dn7ti0MAuNvbuFho5eMDEBPPdvbe==AA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dear Scott,
How to handle table with token?
How to implement this?
Regards,
Yogesh
On Wednesday, March 8, 2017, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Tue, Mar 7, 2017 at 11:55 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com
> <javascript:;>> wrote:
> > On Tue, Mar 7, 2017 at 11:21 PM, Yogesh Sharma <yogeshraj95(at)gmail(dot)com
> <javascript:;>> 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 | Günce Kaya | 2017-03-08 09:13:47 | import CSV file to a table |
| Previous Message | vinny | 2017-03-08 07:54:35 | Re: Postgres, apps, special characters and UTF-8 encoding |