Re: To create or not to create that index

2023-08-17 Thread Stefan Knecht
Ah no it is not. Something else was changed at the same time. Sigh. Thanks for clarifying David On Fri, Aug 18, 2023 at 10:42 AM Stefan Knecht wrote: > But that "invalid" index is being used by queries > > On Fri, Aug 18, 2023 at 10:41 AM David G. Johnston < > david.g.johns...@gmail.com> wr

Re: To create or not to create that index

2023-08-17 Thread David G. Johnston
On Thu, Aug 17, 2023 at 8:43 PM Stefan Knecht wrote: > But that "invalid" index is being used by queries > >> >> Please don't top-post. If it is used by queries it isn't invalid and thus its existence shouldn't be surprising. So I'm not sure what you are saying. David J.

Re: To create or not to create that index

2023-08-17 Thread Stefan Knecht
But that "invalid" index is being used by queries On Fri, Aug 18, 2023 at 10:41 AM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Thu, Aug 17, 2023 at 8:37 PM Stefan Knecht > wrote: > >> Hello >> >> Why does this happen? >> >> profile_aggregates=> create index concurrently foo_i

Re: To create or not to create that index

2023-08-17 Thread David G. Johnston
On Thu, Aug 17, 2023 at 8:37 PM Stefan Knecht wrote: > Hello > > Why does this happen? > > profile_aggregates=> create index concurrently foo_idx on agg (status, > foots, created_ts); > > > ^CCancel request sent > ERROR: canceling statement due to user request > profile_aggregates=> > profile_ag

To create or not to create that index

2023-08-17 Thread Stefan Knecht
Hello Why does this happen? profile_aggregates=> create index concurrently foo_idx on agg (status, foots, created_ts); ^CCancel request sent ERROR: canceling statement due to user request profile_aggregates=> profile_aggregates=> create index concurrently foo_idx on agg (status, foots, create