On Tue, Jan 19, 2021 at 05:37:51PM -0300, Alvaro Herrera wrote:
> I guess you could make the case that the CCI call should be in the
> callers where we actually loop (SetDefaultACLsInSchemas,
> RemoveRoleFromObjectACL), but it's hard to get excited about the added
> clutter.
Yeah, that matches my
Alexander Stoddard writes:
> Thank you for this. I can get different plans by changing the different
> parameters, but if the output of EXPLAIN VERBOSE tells me geqo planning
> specifically is being used I'm not seeing it. Is there a way to see in the
> explain plan if geqo was used?
It's not re
On Tue, Jan 19, 2021 at 2:47 PM Michael Lewis wrote:
> On Fri, Jan 15, 2021 at 3:27 PM Alexander Stoddard <
> alexander.stodd...@gmail.com> wrote:
>
>> I am doing nothing to specify the optimizer. Do I have configurable
>> options in that regard? I was unaware of them.
>>
>
> Read up on join_coll
On Fri, Jan 15, 2021 at 3:27 PM Alexander Stoddard <
alexander.stodd...@gmail.com> wrote:
> The queries are complex, multiple joins to 10 plus tables, although most
> are to tiny enum type lookup tables. I believe it is the join between the
> two large tables that I have described that causes the
On 2021-Jan-15, Michael Paquier wrote:
> On Wed, Jan 06, 2021 at 07:15:24PM +0200, Andrus wrote:
> > Should duplicate schema names accepted or should their usage throw better
> > error messages.
>
> This means that we are one call of CommandCounterIncrement() short for
> such queries, and similar
Thanks for the tip, Jayadevan!
Looks like your suggestion can help med with this.
I’m getting all the info I need from this view.
Cheers,
Bjørn
From: Jayadevan M
Date: Tuesday, 19 January 2021 at 12:33
To: "Myklebust, Bjørn Magnar"
Cc: "pgsql-gene...@postgresql.org"
Subject: Re: How to check
Dear postgreSQL developer Team,
we are curently supporting a couple of SLES12 SP5 Server running different
application
together with postgreSQL10 or postgreSQL11 database including postGIS30
extension.
These server has to be updateted to SLES15 SP2 in the next time, so we are
looking
for a vali
Hi.
I’ve got a materialized view as a source for my ETL-process, and the
materialized view takes several hours to refresh. During which it is locked
for queries.
So I’m looking for a way to identify if the refresh process is finished or if
it’s still running - preferably without having to wait
> On Jan 19, 2021, at 6:33 AM, Jayadevan M wrote:
>
>
>
> So I’m looking for a way to identify if the refresh process is finished or if
> it’s still running - preferably without having to wait for timeout by
> querying a locked materialized view. But by e.g. using the system tables or
>
>
> So I’m looking for a way to identify if the refresh process is finished or
> if it’s still running - preferably without having to wait for timeout by
> querying a locked materialized view. But by e.g. using the system tables
> or otherwise.
>
>
>
> Can anybody suggest some pointers on how to
I’ve got a materialized view as a source for my ETL-process, and the
materialized view takes several hours to refresh. During which it
is locked for queries.
Would it be an option to split the process into a cascade of
materialized views to minimize the actual time of lock?
So I’m lookin
11 matches
Mail list logo
