| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Yogesh Sharma *EXTERN*'" <yogeshraj95(at)gmail(dot)com>, "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 09:24:28 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B53A0691D@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yogesh Sharma wrote:
> 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.
Maybe I misunderstand something, but you don't need to do that because it
happens automatically.
If you run REINDEX, it will take an ACCESS EXCLUSIVE lock on the index
before it starts its work.
That means that it has to wait until all earlier INSERTing transactions are
ended, and all INSERTs that come after the REINDEX will have to wait until
the REINDEX is done.
The database takes care that the data are consistent, so why would you
want to do that explicitly?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2017-03-08 09:47:00 | Re: Postgres, apps, special characters and UTF-8 encoding |
| Previous Message | Günce Kaya | 2017-03-08 09:13:47 | import CSV file to a table |