Re: BUG #5364: citext behavior when type not in public schema

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Markus Wichitill <mawic(at)gmx(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5364: citext behavior when type not in public schema
Date: 2010-06-03 14:13:20
Message-ID: 201006031413.o53EDKH01650@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I have documented this citext limitation with the attached, applied
> > patch.
>
> Are you planning to insert similar verbiage into every other contrib
> module's docs?

Uh, do they all have this odd behavior? Most people assume they would
get an error in such cases, not case-sensitivity.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ None of us is going to be here forever. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-06-03 14:15:38 Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
Previous Message Hartmut Goebel 2010-06-03 14:00:49 Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading