From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Getting fancy errors when accessing information_schema on 10.5 |
Date: | 2018-10-30 14:40:34 |
Message-ID: | d45d02406b2d0bd62f371d726795969841200c69.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Axel Rau wrote:
> nextcloud=> explain select ((pg_has_role(relowner, 'USAGE'::text) OR has_sequence_privilege(oid, 'SELECT, UPDATE, USAGE'::text))) from pg_class;
> QUERY PLAN
> -----------------------------------------------------------
> Seq Scan on pg_class (cost=0.00..28.56 rows=656 width=1)
> (1 row)
>
> nextcloud=> explain select (relkind = 'S'::"char") from pg_class;
> QUERY PLAN
> -----------------------------------------------------------
> Seq Scan on pg_class (cost=0.00..28.56 rows=656 width=1)
> (1 row)
Hm, strange, for me the first query is slightly more expensive (because
of the OR), but the costs are pretty similar.
Another idea I have is to raise the costs of "has_sequence_privilege"
slightly.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-10-30 15:04:47 | Re: Getting fancy errors when accessing information_schema on 10.5 |
Previous Message | Axel Rau | 2018-10-30 14:35:39 | Re: Getting fancy errors when accessing information_schema on 10.5 |
From | Date | Subject | |
---|---|---|---|
Next Message | Surafel Temesgen | 2018-10-30 14:46:49 | Re: COPY FROM WHEN condition |
Previous Message | Sergei Kornilov | 2018-10-30 14:39:45 | Re: [HACKERS] generated columns |