Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)
Дата
Msg-id 20200602213003.GA20290@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-bugs
On 2019-Dec-02, Thomas Munro wrote:

> On Mon, Dec 2, 2019 at 12:32 PM Manuel Rigger <rigger.manuel@gmail.com> wrote:
> > CREATE TABLE t0(c0 TEXT COLLATE "POSIX");
> > CREATE VIEW v0(c0) AS (SELECT (t0.c0 COLLATE "C")::INT FROM t0); --
> > FailedAssertion("!OidIsValid(def->collOid)", File: "view.c", Line: 89)
> >
> > When building without assertions, the CREATE VIEW statement results in
> > an error instead:
> >
> > ERROR: collations are not supported by type integer
> 
> I think the options are to add a check and ereport() instead of an
> assertion, or just remove the assertion and let BuildDescForRelation()
> report the error as it does in non-assert builds.  I think the latter
> is better, since it seems well established that BuildDescForRelation()
> will complain about that via its call to GetColumnDefCollation().
> Here's a patch to do that.

This has not been applied yet AFAICS.  Thomas, are you getting to this
one soon?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-bugs по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: BUG #16462: Update Statement destructive behaviour with joins
Следующее
От: Dave Cramer
Дата:
Сообщение: Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)