From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Shira Bezalel <shira(at)sfei(dot)org> |
Cc: | pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Function not displaying PARALLEL SAFE on SQL tab |
Date: | 2017-01-18 09:36:42 |
Message-ID: | CA+OCxoxwbiD9R=jUdDAo2bZc2uC9RydT4kocOhNiQ9k00+7VDw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Thanks, logged here: https://redmine.postgresql.org/issues/2089
On Tue, Jan 17, 2017 at 6:13 PM, Shira Bezalel <shira(at)sfei(dot)org> wrote:
> I'm reviewing some PostGIS functions in pgAdmin 4. When I click on the SQL
> tab, I notice that the "PARALLEL SAFE" qualifier doesn't show up. But when I
> do an "\sf" on one of these functions in psql, I see the syntax (but not the
> NOT LEAKPROOF). Is this a known issue? I looked through issues list, but
> didn't see anything similar. For now, is the psql output the most accurate?
>
> SQL tab from pgAdmin 4:
>
> CREATE OR REPLACE FUNCTION public.st_intersects(
> geom1 geometry,
> geom2 geometry)
> RETURNS boolean
> LANGUAGE 'sql'
> COST 100.0
> IMMUTABLE NOT LEAKPROOF
> AS $function$
> SELECT $1 OPERATOR(public.&&) $2 AND public._ST_Intersects($1,$2)
> $function$;
>
>
>
> psql output:
>
> mydb=# \sf st_intersects (geometry,geometry)
> CREATE OR REPLACE FUNCTION public.st_intersects(geom1 geometry, geom2
> geometry)
> RETURNS boolean
> LANGUAGE sql
> IMMUTABLE PARALLEL SAFE
> AS $function$SELECT $1 OPERATOR(public.&&) $2 AND
> public._ST_Intersects($1,$2)$function$
>
>
>
>
> Thanks,
>
> Shira Bezalel
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Tammineni | 2017-01-18 19:04:18 | Re: Queries are taking way longer in 9.6 than 9.5 |
Previous Message | Chris Mair | 2017-01-18 00:22:29 | Re: Queries are taking way longer in 9.6 than 9.5 |