Re: hstore dump/restore bug in 9.3

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: hstore dump/restore bug in 9.3
Date: 2014-05-13 04:07:02
Message-ID: 53719A66.7000603@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 05/12/2014 11:48 AM, Tom Lane wrote:
> Also, I think we still have some other dependencies on assumed
> operator names in eg. CASE. Cleaning up only NULLIF may not be a
> full solution.

GREATEST(..) and LEAST(..) already handle this, as does DISTINCT(...).

Is NULLIF different? Or are they doing something suspect, just
differently suspect?

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-05-13 14:33:11 Re: hstore dump/restore bug in 9.3
Previous Message sidharthdeshpande 2014-05-12 23:46:23 BUG #10297: yum - transaction check error