pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: emre@hasegeli.com, Matthias Kurz <m.kurz@irregular.at>
Cc: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Subject: Re: [PATCH] Alter or rename enum value
Date: Sun, 11 Sep 2016 10:34:57 -0400
Message-ID: <23103.1473604497@sss.pgh.pa.us> (raw)
In-Reply-To: <b942ad05-abae-e183-5d28-f6b66ab21a97@BlueTreble.com>
References: <CAO=2mx6uvgPaPDf-rHqG8=1MZnGyVDMQeh8zS4euRyyg4D35OQ@mail.gmail.com>
	<CAO=2mx6rK_h4BC7y+3Nu-8fuZJXdFjd9FE_MZnzkH+vnMp0C-Q@mail.gmail.com>
	<d8ja8ln7nl0.fsf@dalvik.ping.uio.no>
	<d8jk2kn4yn0.fsf_-_@dalvik.ping.uio.no>
	<d8jeg5m4as8.fsf@dalvik.ping.uio.no>
	<CAE2gYzxo4bB_uQDafQYoGx=WmUrO-NFUbKBYfu4j_=LfaaUzFg@mail.gmail.com>
	<d8jy43m2wow.fsf@dalvik.ping.uio.no>
	<CAE2gYzy9fWFmMgnA0DstcGdtuFv40d3JXgtikE-ywtZ2qow=ng@mail.gmail.com>
	<26875.1472935684@sss.pgh.pa.us>
	<CAE2gYzzoWnzmz3MhiSr_49Mjjah4KXju-N81Bjc9p95-YcxpcA@mail.gmail.com>
	<32710.1473099022@sss.pgh.pa.us>
	<CA+Tgmoaz9OSD1Zbf4kMfEDV8OMGM6x2=kWxAxd1XPCfTWW1f8Q@mail.gmail.com>
	<8384.1473186627@sss.pgh.pa.us>
	<9dd58b5f-0447-54fe-02f4-afb62fd7c3c8@dunslane.net>
	<17893.1473193170@sss.pgh.pa.us>
	<d8jk2eoyn5u.fsf@dalvik.ping.uio.no>
	<30073.1473279258@sss.pgh.pa.us>
	<CAO=2mx6wDD3kA+XfJ6Lo9y3ENi3R4v_ZBmatb_58X99A-zQZJg@mail.gmail.com>
	<CAE2gYzy2U60yhj9fpSciO+cF8AVd2_V++d6GZUiC3NeG8sWwvA@mail.gmail.com>
	<b942ad05-abae-e183-5! d28-f6b66ab21a97@BlueTreble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> On 9/8/16 4:55 AM, Emre Hasegeli wrote:
>> The main problem that has been discussed before was the indexes.  One
>> way is to tackle with it is to reindex all the tables after the
>> operation.  Currently we are doing it when the datatype of indexed
>> columns change.  So it should be possible, but very expensive.

> Why not just disallow dropping a value that's still in use? That's 
> certainly what I would prefer to happen by default...

Even ignoring the hidden-values-in-indexes problem, how would you
discover that it's still in use?  Not to mention preventing new
insertions after you look?

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (56+ messages)

Message-ID: <23103.1473604497@sss.pgh.pa.us>
Permalink:  ../23103.1473604497@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23103.1473604497@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Jim.Nasby@BlueTreble.com, m.kurz@irregular.at, ilmari@ilmari.org, andrew@dunslane.net, robertmhaas@gmail.com, david.g.johnston@gmail.com
  Subject: Re: [PATCH] Alter or rename enum value
  In-Reply-To: <23103.1473604497@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox