Alexey,
On Fri, Jun 10, 2011 at 05:46:42PM +0300, Alexey Klyukin wrote:
> Providing my thoughts on the 'mundane' question first.
I was actually referring to this paragraph:
The standing code handled index/constraint dependencies of changing columns by
extracting the SQL definition using pg_g
Noah,
Providing my thoughts on the 'mundane' question first.
On Tue, May 24, 2011 at 1:40 PM, Noah Misch wrote:
>
> I also had a more mundane design question in the second paragraph of [2]. It
> can probably wait for the review of the next version of the patch. However,
> given that it affects
On Tue, May 24, 2011 at 10:10:34AM -0400, Tom Lane wrote:
> Noah Misch writes:
> > PostgreSQL 9.1 will implement ALTER TABLE ALTER TYPE operations that use a
> > binary coercion cast without rewriting the table or unrelated indexes. It
> > will always rewrite any indexes and recheck any foreign k
Noah Misch writes:
> PostgreSQL 9.1 will implement ALTER TABLE ALTER TYPE operations that use a
> binary coercion cast without rewriting the table or unrelated indexes. It
> will always rewrite any indexes and recheck any foreign key constraints that
> depend on a changing column. This is unnece
PostgreSQL 9.1 will implement ALTER TABLE ALTER TYPE operations that use a
binary coercion cast without rewriting the table or unrelated indexes. It
will always rewrite any indexes and recheck any foreign key constraints that
depend on a changing column. This is unnecessary for 100% of core binar
