►
From YouTube: GitLab 13.5 Kickoff - Enablement:Database
Description
Database Kickoff for 13.5.
Planning issue: https://gitlab.com/gitlab-org/database-team/team-tasks/-/issues/90
A
Hi,
I'm
josh
lambert,
the
group
product
manager
for
the
enablement
section
and
I'd
like
to
talk
a
little
about
what
we
are
planning
to
achieve
in
the
get
lab,
13.5
release
that
will
be
available
on
august
october.
22Nd
we're
working
on
a
couple
priorities
here
in
general
priority
order,
the
first
one
is.
We
want
to
make
sure
that
we
continue
to
provide
support
to
the
package
team
as
they
work
on
the
container
registry
schema
and
partitioning.
A
Overall,
we
this
this
is
important
for
us
to
have
more
insight
into
the
storage
and
overall
image
layout
of
the
gitlab
container
registry,
and
so
this
is
really
important
to
have
really
a
number
of
benefits
out
of
that
right.
Now,
it's
fairly
opaque
and
we
have
to
interact
by
api
and
it's
not
very
efficient.
So
this
is
pretty
important
for
a
number
of
initiatives
here
at
get
lab
and
improving
the
overall
user
experience
of
the
registry
next
up.
A
We
also
want
to
continue
to
work
with
the
compliance
team
on
the
ui
ux
changes
needed
to
encourage
really
kind
of
the
osmo
aquarium,
so
we
went
through
and
we
partitioned
actually
the
other
difference
table,
but
we
can't
really
make
use
of
it
until
we
have
the
usage
patterns
of
the
table
that
are
aligned
with
the
partitioning
key,
and
so
the
idea
is
that
we'll
have
some
default
filtering
options
that
can
better
align
with
the
partitioning
keys
and
that
will
overall,
let
us
take
advantage
of
the
table
without
having
performance
impacts
and,
in
fact,
performance
benefits.
A
So
really
we're
kind
of
blocked
here
until
this
lands,
and
then
once
that
happens,
there's
a
bit
more
work
to
do
on
our
side
to
finish
up
the
the
partitioning
work
and
then
this
will
be
done
next
up.
We
want
to
work
on
an
automatic
re-indexing
of
the
standard
indexes.
A
Essentially
right
now
you
can
manually
run
a
repack
on
the
indexes
with
get
lab,
but
you
know
even
if
you're
doing
this-
and
you
know
to
do
it-
you
can
still
end
up
with
a
fair
amount
of
index
bloat.
If
you
don't
do
it
there
frequently
enough
and
of
course,
some
of
our
self-managed
customers
likely
aren't
aware
that
they
have
to
do
this
in
the
first
place.
So
it
would
be
great
if
we
can
take
advantage
of
this
ourselves
automatically
for
all
of
our
customers.
A
You
can
see
here
that
we
are
currently
enabling
the
merge
request,
diff
external
request
files,
and
this
is
causing
a
significant
amount
of
index
bloat,
and
so
we
are
working
on
this
at
a
fairly
high
priority
here
in
13.5
to
help
target
some
of
this
index
bloat,
and
so
google
working
on
two
items
in
particular,
automatically
select
the
indexing
for
re-indexing
and
also
detecting
a
block
situation
and
cancel
the
process,
so
we're
working
on
those
two
things
here
to
start
to
be
able
to
support
this
automatic
re-enlisting
process.
A
A
A
This
is
a
table
that
is
getting
quite
big
and
we
are
at
risk
of
actually
running
out
of
the
primary
key
size,
and
so
we
are
working
on
partitioning
it
to
help
improve
performance
and
scalability,
as
this
is
the
table
that
tracks
essentially
everything
all
users
have
ever
done
in
gitlab
on
github.com,
and
so
it
is
quite
big,
but
we
also
don't
want
to
lose
activity
as
well,
so
we
are
working
to
make
sure
it
continue
to
scale
in
the
future.