Re: [GENERAL]
| От | Jaime Soler |
|---|---|
| Тема | Re: [GENERAL] |
| Дата | |
| Msg-id | CAKVUGgTwF3E14Qa65fRF051M7MqF=n=w6NJMSh32oy93gbGBCA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] (Yogesh Sharma <yogeshraj95@gmail.com>) |
| Ответы |
Re: [GENERAL]
|
| Список | pgsql-general |
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@gmail.com>:
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@gmail.com> wrote:On 21 December 2016 at 09:59, Yogesh Sharma <yogeshraj95@gmail.com> 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.
В списке pgsql-general по дате отправления: