Re: Check constraints and function volatility categories

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Dane Foster <studdugie(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Check constraints and function volatility categories
Date: 2016-02-01 19:41:09
Message-ID: 56AFB4D5.9030602@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 02/01/2016 11:17 AM, Dane Foster wrote:
> Hello,
>
> I'm discovering that I need to write quite a few functions for use
> strictly w/ check constraints and I'm wondering if declaring the
> volatility category for said functions will affect their behavior when
> invoked by PostgreSQL's check constraint mechanism.
>
> Essentially what I'm trying to figure out is if volatility categories
> increase or decrease the latency of executing check constraints. I've
> done some micro benchmarks but I have no experience benchmarking
> anything in PostgreSQL to trust that I'm measuring the right thing. So
> I'm asking the experts.

The above is sort of backwards. You need to ask what the function does
and from that determine what is the most appropriate volatitity
category. For more detailed info see:

http://www.postgresql.org/docs/9.5/interactive/xfunc-volatility.html

It would help to see some samples of the actual functions.

>
> I'm running PostgreSQL 9.5 on Ubuntu Linux 15.10. I don't know if this
> matters but this is my workstation which is a pretty zippy AlienWare X51
> w/ 16GB RAM on a Core i7-4770 processor.
>
> Thanks,
>
> Dane

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message melvin6925 2016-02-01 19:45:30 Re: strange sql behavior
Previous Message Bill Moran 2016-02-01 19:41:08 Re: strange sql behavior