Re: plans for PostgreSQL 12

From: Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plans for PostgreSQL 12
Date: 2018-06-04 07:59:11
Message-ID: 709891ff-a0e8-04e4-20a1-bb80bcc2a37e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/06/18 09:37, Pavel Stehule wrote:
>
>
> 2018-06-04 9:24 GMT+02:00 Heikki Linnakangas <hlinnaka(at)iki(dot)fi
> <mailto:hlinnaka(at)iki(dot)fi>>:
>
> On 04/06/18 09:12, Pavel Stehule wrote:
>
> It requires introduction of new "safe" functions (& operators).
> Immutable
> functions are not enough safe.
>
> CREATE OR REPLACE FUNCTION public.fx()
>   RETURNS integer
>   LANGUAGE plpgsql
>   IMMUTABLE
> AS $function$
> BEGIN
>    RETURN (SELECT count(*) FROM pg_class);
> END;
> $function$
>
> postgres=# SELECT fx();
> ┌─────┐
> │ fx  │
> ╞═════╡
> │ 343 │
> └─────┘
> (1 row)
>
>
> That function is incorrectly marked as IMMUTABLE. In that situation,
> it's enough that we throw a sane error like "ERROR: no snapshot
> available".
>
> Yes, it is incorrect mark. Unfortunately - this is often workaround for
> wrong estimations - so I afraid, in this case, your proposed fix breaks
> lot of applications.

I would say such applications are already broken.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-06-04 08:32:47 Spilling hashed SetOps and aggregates to disk
Previous Message Pavel Stehule 2018-06-04 07:37:02 Re: plans for PostgreSQL 12