►
From YouTube: GitLab 15.9 Kickoff - Enablement: Database
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody,
my
name,
is
Roger
and
welcome
to
the
database.
Group's
15.9
planning
today
with
me
is
Alex,
say:
Hello
Alex,
Hello
Alex.
Thank
you,
Alex.
Sorry,
we're
gonna
go
through
what
we've
got
planned
and
kind
of
where
we
are
currently
and
some
of
the
new
directions
we're
thinking
about
taking
some
exploration.
So
for
starters,
in
15.9,
our
team
continues
to
not
be
at
full
capacity.
A
We've
got
two
out
of
our
seven
members,
proceeding
with
onboarding
and
ramping
up
and
we're
expecting
to
be
fully
capacity
in
about
two
more
milestones
for
some
of
the
things
we're
looking
at
a
lot
of
these
thieves
continue
forward
from
before
one
is
looking
at
our
batch
background,
migrations
and
the
general
directional
theme
we
want
to
aim
for
here
is
to
help
our
users
understand
how
long
a
batch
Micron
citation
might
take,
and
just
some
estimates
that
we
think
will
help
people
better
plan
their
upgrade
path.
B
Yeah,
the
other
critical
part
that
we're
hoping
to
wrap
up
in
this
upcoming
Milestone
is
parallelization
so
running
more
than
one
background
migration
at
a
time,
and
we
hope
that
this
will
not
only
speed
up
our
own
migrations,
but
also
for
our
customers,
especially
those
running
them
bit
in
the
background,
will
allow
them
to
execute
these
migrations
more
quickly,
but
still
maintain
the
safety.
So.
A
Cool
yeah,
that's
super
exciting.
The
next
item
here
we
have
is
CI
partitioning
support,
so
we've
been
working
to
sort
of
help
partition
these
tables
on
gitlab
that
are
just
getting
bigger
and
bigger,
and
the
idea
here
is
once
we
set
up
some
basic
foundations.
We
want
to
make
sure
we
can
partition,
basically
everything
by
default,
leveraging
existing
tooling
that
we're
developing
yeah
I'll.
Let
Alex
dive
into
a
bit
more
detail
here
as
well.
B
Yeah
we've
made
some
good
progress
on
CI
partitioning
in
the
last
Milestone,
we're
very
close
to
adding
the
zero
partition
for
our
largest
database
table
CI
built,
and
we
were
really
hoping.
We
would
get
that
one
done
this
Milestone,
but
it's
it's
very
big
and
it's
very
complicated
and
even
just
building
new
indexes
on
it
has
proven
challenging.
So
it's
it's
going
slow,
but
we're
we've
made
some
good
progress
and
I
think
well
we're
we're
really
hoping
to
get
that
partitioning
done
in
1509
and.
A
B
Yeah
yep,
so
zero
partitioning
here
means
that
we
will
have
a
single
partition,
but
it
will
be
with
it.
The
table
will
be
partitioned,
but
only
with
one
partition,
so
the
application
has
to
work
as
though
it's
a
partition
table
and
then
we'll
introduce
additional
partitions
in
the
future
and
we'll
be
able
to
use
them
for
all
sorts
of
stuff,
like
that
retention,
guiding
and
guidance
and
and
that
kind
of
thing
for
people
who
want
to
drop
old
logs
and
stuff
like
that,
so
cool.
B
That
is,
that
is
a
spot
on
description
of
what
we're
trying
to
accomplish
here.
Database
review
is
a
complicated
and
difficult
part
of
our
process
here
internally
for
getting
code
merged,
and
this
automated
testing
is
aimed
at
alleviating
some
of
those
issues,
specifically
we're
hoping
to
make
a
lot
more
progress
now
on
query
reporting
and
getting
the
those
new
queries
actually
recorded
and
and
reported
in
a
meaningful
way.
I
don't
know.
A
And
then,
lastly,
we
have
two
priority
issues.
We
would
just
like
to
highlight
and
call
out
so
the
first
one
here
is
about
removing
old
migrations
and
we've
started
some
of
this
process,
but
clearly
it's
it's
not
yet
complete
and
part
of
this
I
think
is
again
following
our
theme
of
trying
to
automate
and
make
easy
repetitive
tasks.
A
I
know
John
has
invested
in
some
tooling
and
modernized
some
of
it
so
that
we
can
start
squashing
some
of
these
things
and
then.
Secondly,
the
priority
area
here
for
Diogo
is
to
help
us
start
to
identify
database
tables
that
don't
match
our
schema
expectations
and
we're
hoping
this
as
a
broader
theme
will
help
us
again
improve
the
resiliency
and
stability
of
our
system,
because
what
we
expect
is
what
our
system
actually
has
Alex
anything
else
you
want
to
you
want
to
highlight
here.
B
Yeah
I,
just
wanna,
there's
an
exciting
new
addition
to
our
remove
migrations
in
15
is
because
we
added
the
required
stop
in
15
4
We're.
B
Actually,
we've
expanded
the
scope
of
that
issue
very
slightly
to
take
us
all
the
way
to
that
required
stop,
rather
than
stopping
at
the
previous
required
stop
when
we,
which
is
when
we
filed
this
issue,
partly
because
that
gets
us
a
little
bit
more
out
of
this
automation
right
at
the
beginning
and
partly
because
it
means
we've
been
able
to
update
and
augment
our
required
stop
process
so
that
those
required
stops
will
be
better
enforced
when,
when
folks
are
actually
making
them-
and
you
can
we'll
expect
to
see
some
documentation
around
those
two
which
is
going
to
be
really
good,
I.