Hi
I had another question, what about when the primary key is a foreign key in
another table? Is the only option to drop the FK and recreate it after the
primary key has been created with the new index?
Thanks!
RV
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Concurren
> -Original Message-
> From: rverghese [mailto:ri...@hotmail.com]
> Sent: Thursday, February 09, 2012 12:49 PM
> To: pgsql-sql@postgresql.org
> Subject: Re: Concurrent Reindex on Primary Key for large table
>
> Thanks! That worked.
>
> Any thoughts about containing index bloat. I thought
Thanks! That worked.
Any thoughts about containing index bloat. I thought the autovac would clean
it up a bit more. Would any tweaks to my settings improve autovac
performance? I am still doing a couple of concurrent reindexes per week
otherwise performance degrades over a couple of days.
Thank
rverghese wrote on 08.02.2012 19:07:
I have a large table with about 60 million rows, everyday I add 3-4 million,
remove 3-4 million and update 1-2 million. I have a script that reindexes
concurrently a couple of times a week, since I see significant bloat. I have
autovac on and the settings are
I have a large table with about 60 million rows, everyday I add 3-4 million,
remove 3-4 million and update 1-2 million. I have a script that reindexes
concurrently a couple of times a week, since I see significant bloat. I have
autovac on and the settings are below. I can't concurrently reindex the
