Re: BUG #4812: statistics not available on tables containing only hstore column

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: George Su <george(dot)su(at)efrontier(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4812: statistics not available on tables containing only hstore column
Date: 2009-05-19 08:32:59
Message-ID: 4A126EBB.2000208@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> I think that code probably originated at a time when palloc(0) threw an
> error, and was meant to avoid any corner-case failures in the subsequent
> logic. I can't get very excited about the case --- it seems to me the
> *real* fix for this complaint is to give hstore some ANALYZE support ---

Possibly. The standard type analyze function is not used for hstore
because it doesn't have an equals operator.

> but if you've tested that it behaves sanely with no columns I have no
> objection to committing it.

Committed.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Damien Guignard 2009-05-19 09:54:54 BUG #4815: max_connections setting has no impact
Previous Message Tom Lane 2009-05-18 22:57:40 Re: distinct on doesn't fail without order by? why?