On Tue, Jul 10, 2012 at 10:44 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Greg Stark st...@mit.edu writes:
On Sat, Jul 7, 2012 at 4:53 AM, Gurjeet Singh singh.gurj...@gmail.com
wrote:
All we need to do is allow swapping of pg_class.relfilenode of two
indexes.
Fwiw I don't like swapping
On Tue, Jul 10, 2012 at 11:11 AM, Greg Stark st...@mit.edu wrote:
On Tue, Jul 10, 2012 at 3:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem you describe is one of constraints and dependencies and
not one of indexes. It seems what you really want is a way to alter
foreign key
On Sat, Jul 7, 2012 at 4:53 AM, Gurjeet Singh singh.gurj...@gmail.com wrote:
All we need to do is allow swapping of pg_class.relfilenode of two indexes.
This will let the dependency entries stand as they are and allow us to drop
the bloated primary key index structure without having to rebuild
Greg Stark st...@mit.edu writes:
On Sat, Jul 7, 2012 at 4:53 AM, Gurjeet Singh singh.gurj...@gmail.com wrote:
All we need to do is allow swapping of pg_class.relfilenode of two indexes.
Fwiw I don't like swapping relfilenodes on indexes the user created.
REINDEX currently does this but it's a
On Tue, Jul 10, 2012 at 3:44 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem you describe is one of constraints and dependencies and
not one of indexes. It seems what you really want is a way to alter
foreign key dependencies to depend on a new index. Either an explicit
command that lets
Excerpts from Tom Lane's message of mar jul 10 10:44:03 -0400 2012:
All of these things seem like ugly, hard-to-use kluges anyway (the
make-sure-the-indexes-match business is just as much of a PITA for the
DBA as it is for the system). What we really want is REINDEX
CONCURRENTLY.
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Tom Lane's message of mar jul 10 10:44:03 -0400 2012:
What we really want is REINDEX CONCURRENTLY.
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.47.9961 ?
Hm ... that paper looks like something we might want to