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

Re: string_to_array has to be stable?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: string_to_array has to be stable?
Date: 2010-07-29 17:10:28
Message-ID: 27322.1280423428@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Jul 29, 2010 at 1:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Or we could decide that volatile domain CHECK expressions are un-sensible
>> and just relabel all these input functions as stable, which would make
>> everything consistent. Thoughts?

> Aren't volatile CHECK expressions pretty un-sensible in general?

Yeah, probably so.  I can't think of a use-case that seems like it would
justify the possible performance hit from having to assume all functions
performing datatype input calls are volatile.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2010-07-29 17:12:06
Subject: Re: On Scalability
Previous:From: Vincenzo RomanoDate: 2010-07-29 17:08:52
Subject: On Scalability

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