Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: disabling an index without deleting it?

  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
  • Cc: "Joshua D. Drake" <jd(at)commandprompt(dot)com>, "Peter Koczan" <pjkoczan(at)gmail(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com>, "pgsql-performance" <pgsql-performance(at)postgresql(dot)org>
  • Subject: Re: disabling an index without deleting it?
  • Date: Wed, 27 Feb 2008 18:37:44 -0500
  • Message-id: <12354.1204155464@sss.pgh.pa.us> <text/plain>
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> If xact A is using a snapshot from before the commit of the index
> DROP, it shouldn't see anything done after the drop anyway.  If
> it's using a snapshot from after the DROP, it won't see the index.
> xact B would only fail to update the index if it was using a
> snapshot after the drop, so I'm having trouble grasping the
> sequence of events where this is a problem.  Could you outline
> the series of events where the problem occurs?

You're assuming that the query plan is as new as the snapshot is.
This isn't guaranteed, at least not without the locking that you
seek to eliminate.

			regards, tom lane
Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group