Search Postgresql Archives
Re: Use case stuck due to Partitioning
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Use case stuck due to Partitioning
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Mon, 28 Jun 2021 13:51:49 -0600
Cc
: PostgreSQL General <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to
: <CA+ERcR-=TMwGsvs4epdi84f+ZL-_4qycDFN=rGR8owGUFW-yBg@mail.gmail.com>
References
: <CA+ERcR-=TMwGsvs4epdi84f+ZL-_4qycDFN=rGR8owGUFW-yBg@mail.gmail.com>
Do you have an index on the "updated_at" field and found that the query is too slow? Do you have an example query?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
Re: Use case stuck due to Partitioning
From:
Shubham Mittal
References
:
Use case stuck due to Partitioning
From:
Shubham Mittal
Prev by Date:
Use case stuck due to Partitioning
Next by Date:
Re: Use case stuck due to Partitioning
Previous by thread:
Use case stuck due to Partitioning
Next by thread:
Re: Use case stuck due to Partitioning
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
