Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: disabling an index without deleting it?
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Jeff Davis <pgsql(at)j-davis(dot)com>
- Cc: "Joshua D. Drake" <jd(at)commandprompt(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Peter Koczan <pjkoczan(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: disabling an index without deleting it?
- Date: Wed, 27 Feb 2008 15:02:46 -0500
- Message-id: <6515.1204142566@sss.pgh.pa.us> <text/plain>
Jeff Davis <pgsql(at)j-davis(dot)com> writes: >>> begin; >>> drop index abc_dx; >>> select .... >>> rollback; > It may cause catalog bloat though, right? Not in this particular case; AFAIR this will only result in catalog row deletions, not updates. So when the deletions roll back, there's no dead rows to clean up. regards, tom lane
- References:
- disabling an index without deleting it?
- From: Peter Koczan
- Re: disabling an index without deleting it?
- From: Scott Marlowe
- Re: disabling an index without deleting it?
- From: Joshua D. Drake
- Re: disabling an index without deleting it?
- From: Tom Lane
- Re: disabling an index without deleting it?
- From: Jeff Davis
- disabling an index without deleting it?
- Prev by Date: t1.col like '%t2.col%'
- Next by Date: Re: Optimizing t1.col like '%t2.col%'
- Previous by thread: Re: disabling an index without deleting it?
- Next by thread: how to identify expensive steps in an explain analyze output
- Indexes: