On Wed, Mar 03, 2021 at 01:20:51AM +, Nagaraj Raj wrote:
> I was trying to collect table metadata with a description; the use case is
> that I need to show all columns of the tables whether it has the description
> or not.
> I tried the below query, but it only gives column details that have
Hi Everyone,
I was trying to collect table metadata with a description; the use case is that
I need to show all columns of the tables whether it has the description or not.
I tried the below query, but it only gives column details that have a
description and ignore others if not.
Postgres 11 |
On Wed, 3 Mar 2021 at 10:04, Michael Lewis wrote:
> Are there guidelines or principles you could share about writing the group by
> clause such that it is more efficient?
If you have the option of writing them in the same order as an
existing btree index that covers the entire GROUP BY clause (i
>
> If we want to do anything much smarter than that like trying every
> combination of the GROUP BY clause, then plan times are likely going
> to explode. The join order search is done based on the chosen query
> pathkeys, which in many queries is the pathkeys for the GROUP BY
> clause (see standa
Hi, I have to configure a postgresql in high availability.
I want to ask you what tool you recommend to manage replication and
failover or switchover.
Thanks.
Regards.-
Pablo.
On Tue, 2 Mar 2021 at 21:53, Liu, Xinyu wrote:
> *Expected Behavior
>
> Since these two queries are semantically equivalent, we were hoping that
> PostgreSQL would evaluate them in roughly the same amount of time.
> It looks to me that there is a missing optimization rule related to pushing
> th
On Tue, 2 Mar 2021 at 21:53, Liu, Xinyu wrote:
> *Expected Behavior
>
> Since these two queries are semantically equivalent, we were hoping that
> PostgreSQL would evaluate them in roughly the same amount of time.
> It looks to me that different order of group by clauses triggers different
> pla
út 2. 3. 2021 v 9:53 odesílatel Liu, Xinyu napsal:
>
>
>
>
>
>
>
>
>
>
> * Hello, We have 2 TPC-H queries which fetch the same tuples but have
> significant query execution time differences (4.3 times). We are sharing a
> pair of TPC-H queries that exhibit this performance difference: First
> que
Hello,
We have 2 TPC-H queries which fetch the same tuples but have significant query
execution time differences (22.0 times).
We are sharing a pair of TPC-H queries that exhibit this performance difference:
First query:
SELECT"orders3"."o_comment",
"orders3"."o_orderstatus",
Hello,
We have 2 TPC-H queries which fetch the same tuples but have significant query
execution time differences (4.3 times).
We are sharing a pair of TPC-H queries that exhibit this performance difference:
First query:
SELECT "ps_comment",
"ps_suppkey",
"ps_supplycost",
10 matches
Mail list logo
