Re: Assertion failure in get_attstatsslot()

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assertion failure in get_attstatsslot()
Date: 2010-07-09 22:49:27
Message-ID: 1278715730-sup-1347@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Tom Lane's message of vie jul 09 12:16:42 -0400 2010:

> If anybody feels really uncomfortable with that, we could add a
> compensating "Assert(IsBinaryCoercible(ARR_ELEMTYPE(statarray),
> atttype))" into get_attstatsslot(). Not sure if it's worth the cycles.

Cycles spent only in assert-enabled builds? Why not?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-07-09 23:08:09 Re: Assertion failure in get_attstatsslot()
Previous Message Tom Lane 2010-07-09 21:21:54 Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms().