Skip site navigation (1) Skip section navigation (2)

Re: Text-any concatenation volatility acting as optimization barrier

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Text-any concatenation volatility acting as optimization barrier
Date: 2012-02-08 13:23:33
Message-ID: CA+TgmoZZfyutLkUeK9gWvVfVznYRt88pgrkYhbqdgoipQTBoyw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers 
On Wed, Feb 8, 2012 at 4:53 AM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
> Patch attached (in git am format). Passes all regression tests (except
> 'json' which fails on my machine even on git master).

Can you provide the diffs from the json test on your machine?  I don't
see any build-farm failures off-hand...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Peter GeogheganDate: 2012-02-08 13:33:30
Subject: Re: Progress on fast path sorting, btree index creation time
Previous:From: Robert HaasDate: 2012-02-08 13:17:43
Subject: Re: Can PQstatus() be used by Application to check connection to postgres periodically?

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group