►
From YouTube: 2020 08 04 Database Team weekly
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
Welcome
to
the
database
team
weekly
meeting,
we
jump
right
into
it.
So
if
you
didn't,
I'm
gonna
verbalize
it
anyway.
If
you
didn't
know,
pat,
maybe
you
don't
know
because
you
just
got
back
but
friday
august
14th
is
another
friends
and
family
day
so
plan
accordingly
and
enjoy
going
back
through
our
retro
from
last
week.
Do
do
we
have
an
issue
anywhere
for
executing
migrations
in
ci
with
an
unprivileged
user?
I
don't
think
we
do.
A
C
B
Yeah,
this
is
something
that
andreas
kind
of
mentioned
that
I
could
help
out
with.
While
he's
out,
I
have
to
look
at
a
little
bit
more
closely.
B
Again,
it's
for
the
there's
the
way
the
automatic
partition
creation
is
there's
a
couple
different
methods.
It
does
there's
a
cron
and
it
runs
on
the
application
startup,
and
I
think
andreas
was
saying.
Since
the
application
startup
is
frequent
enough.
We
don't
need
to
have
the
quran
running.
I
think,
or
something
like
that,
so
he
just
figured
that
that
could
be
disabled
in
production.
B
A
All
right
and
I
think,
for
our
goals
last
week
it
was
mostly
pretty
honest
to
keep
his
head
above
water
being
the
lone
person.
Here
there
were
a
few
items
that
got
closed.
Is
there
anything
major
you
want
to
review?
To
be
honest,.
C
Oh,
no,
I'm
sorry
so
so
many
reviews.
I
tried
to
keep
up
with
all
the
issues
database
issues
both
on
patrick's
issues
and
others.
So
I
try
to
comment
everywhere,
but
yeah.
No
real.
A
D
A
Jose
jumping
back
to
your
topic
here:
are
there
any
specific
questions
that
you
had?
We
just
talked
about
it
briefly,
but
we
can
recap.
If
you
have
any
specific
questions.
D
Yes,
I'd
just
like
to
give
a
bit
of
overview
on
that.
It's
about
this
change
that
I
see.
There's
plenty
of
ruby
code
that
you're
changing
to
enable
like
table
partitioning.
I
guess
in
the
rails,
application
and
like
the
andreas
did
a
comment
for
infrastructure
there.
If
you
would
like
to
review
or
participate
with
you
guys
and
okay,
if
you're
applying
something
in
the
database,
please
let
me
know
or
any
parameter
if
you
want
us
to
monitor
this
during
the
meantime,
it's
great,
but
on
the
ruby.
Unfortunately,
I'm
not
a
specialist
on
that.
D
Yeah,
the
only
two
comments
I
did
that
is
like
before
we
roll
out
this.
Let's
keep
an
eye
with
the
sari
on
call,
because
I
believe
that
if
we
have
something
wrong
here,
we
will
have
more
errors
on
the
rails
application
initially,
because
we
don't
create
those
kind
of
partitions
all
the
time
right
right.
A
A
All
right
and
for
this
week
I
figured
we'd
just
run
through
what's
in
13-3
since
hummus,
it
has
helped
now
and
pat
just
got
back
this
week,
I'm
going
to
start
from
the
bottom
up,
so
the
conflict-free
version
handling
how's
it
going
pat.
B
Yeah
that
was
merged
in
so
I
really
was
just
kind
of
waiting
to
make
sure
that
everything
seems
good
with
it.
But
at
this
point
I
think
we're
you
know,
there's
a
few,
maybe
follow-ups
from
it,
but
everything
is
looking
pretty
good.
There
haven't
been
any
serious
issues
or
anything,
so
I
think
that
one
probably
we
can
close
out
and
probably
the
related
announcement
issue,
keep
open
a
little
bit
longer
in
case
people
want
to
comment,
but
it's
pretty
good.
A
Got
it
pat.
B
A
All
right
that
one
is
andreas
and
giannis
yeah.
C
A
Do
you
have
any
questions
or
need
any
help
with
that?
One.
A
B
Yeah
that
one
was
just
kind
of
a
sanity
check
to
make
sure
that
the
feature
team
doesn't
update
the
audited
event
schema,
which
would
break
the
partitioning
stuff
that's
happening,
but
I
think
also
that
looked
like
giannis
mummy
commented
that
they
added
a
test
for
that
themselves.
So
maybe
we
don't
need
that
anymore.
Yeah.
C
We
added
the
specs,
so
I
just
pinged
you
there
so
that
we
can.
We
should
check
if
anything
else
is
needed.
I
don't
think
that
we
need.
A
C
Any
additional
things
I
think,
that
the
the
specs
that
we
added
cover
most
of
the
cases.
C
C
C
But
the
quick
checks-
I
I
I've
done-
show
that
everything
must
be
okay,
but
we
have
to
be
thorough.
A
Okay,
this
one's
likely
gonna
slide
out.
This
is
new.
Well,
we've
talked
about
it,
but
container
registry
has
come
in.
A
I
don't
know
if
you
all
saw
the
epic
in
issues
for
that
one,
so
they're
creating
a
new
database
schema
for
it,
and
we
need
to
look
at
it
with
partitioning
in
mind
before
they
actually
deploy
it.
It's
going
to
be
easier
to
build
it
and
then
build
it
and
then
migrate
it
into
partitioning
later
on.
So
this
one
probably
need
to
kick
out
to
13
for
right.
Josh
container
registry
is
higher
priority.
E
That
means
we
basically
need
to
keep
track
of
what
layers
are
part
of
what
images
and
how,
because
you
can
share
layers
across
images,
and
so
it's
not
an
easy,
simple
tweet
operation,
you
kind
of
have
to
sort
of
you
know,
sort
of
like
a
reference,
call
type
thing,
anyways
long
story
short.
We
have
to
build
our
own
database
to
to
basically
track
all
these
things.
Then
we
know
what
we
can
delete
and
what
we
can't.
E
E
So
that's
that's
the
reason
for
urgency
here
right
now,
it's
planned
to
hopefully
be
delivered
in
january-ish
as
far
as
you'll
actually
run
a
delete
operation
on
this.
But
you
know
the
longer
this
database
operation
takes
or
the
longer
this
in
the
state
of
the
sovereignty
takes
the
obviously
the
further
pushed
out
that
will
be
and
the
the
later
we
can
realize
any
savings
and
the
more
expensive
it
will
be
become,
as
the
container
registry
continues
to
grow.
A
B
Yeah,
it's
pretty
small
change
and
we
might
be
able
to
fit
it
in
still,
but
suddenly
it's
like
a
super
high
priority.
A
Okay,
we've
gotten
through
everything
in
a
very
efficient
manner
today.
So
are
there
any
other
topics
anybody
wants
to
cover
for
the
day.