tributing a post are outlined in
the invite, but please feel free to reach out to me if you have any
questions.
https://www.softwareandbooz.com/pgsql-phriday-001-invite/
Regards,
Ryan Booz
In a recent update (not sure when), the default for DBeaver seems to have
changed so that the navigator view is set to "simple", rather than
"advanced" which shows all objects.
Right-click the server -> edit connection -> Select "General" -> verify
"Navigator View"
On Fri, Oct 29, 2021 at 9:48
As for clustering, unfortunately, it's a one-time operation in Postgres (as
far as I'm aware), so you'd have to "cluster" the index every time after an
insert or update of data. If it is partitioned, I presume it can be run on
the index of each partition table individually - but I'm not sure.
On M
Heh, I honestly forgot about the recursive CTE. Certainly worth a try and
wouldn't require installing other extensions.
This is what depesz is referring to:
https://wiki.postgresql.org/wiki/Loose_indexscan
On Thu, Sep 23, 2021 at 3:04 AM hubert depesz lubaczewski
wrote:
> On Wed, Sep 22, 2021 a
Index Cond: (station > NULL::text)
Heap Fetches: 19
HTH,
Ryan
On Wed, Sep 22, 2021 at 6:22 PM Israel Brewster
wrote:
> On Sep 22, 2021, at 2:05 PM, Ryan Booz wrote:
>
> Ah. I didn't realize that. If SkipScan was chosen, you'd actually see it
&g
gt; On Sep 22, 2021, at 1:50 PM, Ryan Booz wrote:
>
> Cool. I'd be interested to see the explain on it if you ever try it again.
> On that cardinality, I'd expect it to be really fast, so I'm interested to
> see if the (SkipScan) nodes were actually used.
>
>
> Wit
Cool. I'd be interested to see the explain on it if you ever try it again.
On that cardinality, I'd expect it to be really fast, so I'm interested to
see if the (SkipScan) nodes were actually used.
On Wed, Sep 22, 2021 at 5:35 PM Israel Brewster
wrote:
>
> On Sep 22, 20
[Timescale Dev Advocate here]
I realize this might not be the most accepted answer (could be interpreted
as trying to "sell" something), but feels like an opportunity to talk about
DISTINCT queries and opportunities. Because you have that index,
Timescale 2.3 added a "Skip Scan" query planner node
