Search Postgresql Archives

Re:

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

 



Dear All, 

I understood below point and i will do the same on my system.

Can i close db session before REINDEX operation and again start db session after REINDEX completed?


Regards,
Yogesh

On Wednesday, December 21, 2016, Jaime Soler <jaime.soler@xxxxxxxxx> wrote:
if you want to reduce the impact of reindex in your inserts and updates operations why don't you try drop index and  CREATE INDEX CONCURRENTLY.
As Alban said you I don't recommend you to execute reindex every hour, at least try to reduce the scope of the reindex to the minimal object.





2016-12-21 12:51 GMT+01:00 Yogesh Sharma <yogeshraj95@xxxxxxxxx>:
Dear Alban,

In my production system, there are lot of read write operation performed every hour. 
So, i am thinking, if i can add check during REINDEX operation nothing update and insert operation performed.
Is it possible?

Regards,
Yogesh

On Wednesday, December 21, 2016, Alban Hertroys <haramrae@xxxxxxxxx> wrote:
On 21 December 2016 at 09:59, Yogesh Sharma <yogeshraj95@xxxxxxxxx> wrote:
> Also, every hour,i am performing VACUUM and REINDEX operation on table.

Why are you running REINDEX every hour? That's a very unusual thing to
do, you'd need a pretty good reason for that.

--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.


[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