Search Postgresql Archives

Re: Request to confirm which command is use for exclusive operation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 7, 2017 at 11:21 PM, Yogesh Sharma <yogeshraj95@xxxxxxxxx> 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.


​You want to exclusively lock a table during every insert just because something might run a concurrent reindex?

If you want to write a higher-level locking scheme for your system and not use what is provided natively by PostgreSQL that's your choice.  Its not worth volunteering my time to help do that, though.  The docs have considerable info regarding explicit locking using the LOCK command.  You should start there.

I see in a subsequent response that you have doubts that REINDEX is actually working properly.  If you are able to demonstrate that maybe the underlying problem could be addressed.

David J.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux