Hello all
Does anyone have an explanation for this?
Query uses only three columns of the table "snap" and all three are in an
index.
The planner seems to think that some partitions are better scanned in full.
Yet for the other half of them it's using the index just fine.
Can someone enlighten m
gt;Heap Fetches: 0
That is, unless it doesn't consider that fact when costing?
On Thu, Apr 23, 2020 at 5:01 PM Andreas Kretschmer
wrote:
>
>
> Am 23.04.20 um 10:13 schrieb Stefan Knecht:
> > Seq Scan on snap_20200225 s (cost=0.00..1.19 rows=1 width=12)
>
> the pa
Okay I'll bite.
Comparing Postgres with Oracle is a bit like comparing a rubber duck you
might buy your three year old, with a 30 ton super tanker.
Do they both float? Yeah, but that's about the only similarity.
The rubber duck barely tells you how and why it floats, but the super
tanker is
You should be able to do something with this if you require it to be done
with COPY:
https://paquier.xyz/postgresql-2/postgres-9-3-feature-highlight-copy-tofrom-program/
But, as David suggested, I'd also recommend to do an intermediate step, and
load the data into a table, or pre-process the file
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
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?
>>
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 <
> d
