►
From YouTube: Database Group Meeting - 2022-05-04
Description
This is the regular application database team meeting, where we discuss team matters and review ongoing work.
A
B
Welcome
to
the
tuesday
april
5th
2022
database
team
meeting
a
quick
reminder
at
the
end
of
the
meeting.
We're
going
to
do
a
quick
short
mini
live
retro.
So,
while
we're
talking
just
think
about
something
positive
from
last
week
and
think
about
something
that
could
have
gone
better
from
the
last
week
and
we'll
talk
about
it,
then
cool
so
infradev
issues,
I
don't
think
there
are
any
today,
looks
like
there
are
none
how
exciting.
C
D
C
B
B
So
we
haven't
announced
it
yet
because
we're
still
gonna
add
a
cop
or
a
test
or
something
that
will
check
to
make
sure
people
have
added
their
tables
as
files
before
they
converge
and
then,
after
that,
I'm
gonna
file
issues
for
all
of
the
teams
that
have
tables
that
were
assigned
in
future
categories
to
go
through
and
check
their
their
tables
to
see
if
they're
assigned
correctly
so
yeah.
So
that's
cool
to
have
some
progress
there,
andreas,
how
auto
vacuum
running.
E
E
C
F
A
So
about
the
improved
batches
background
migration
log.
So
when
I
was
doing
a
documentation,
so
we
have
a
section
that
it's
called
like
the
debugging
and
I
found
that
we
are
not
logging.
All
of
the
parameters
to
our
old
blocks
about
the
battery
background
migrations,
for
example,
the
class
name,
job
parameters
etc.
And
I
just
created
an
mr,
where
we
are
adding
these
fields
to
the
logs.
B
G
Small
plant,
a
small
note
on
that,
even
though
we
switched
the
martial
is
back
as
a
technical
writer,
because
we
started
the
review
with
amy.
I
think
that
you
can
continue
the
review
with
amy,
because
this
is
a
large
document.
It's
350
lines,
so
there's
no
no
need,
if
she's
already
on
top
of
it
and
yeah.
B
A
C
B
B
Just
a
reminder
that
dimitri
is
available
as
a
back-end
maintainer
for
batch
background,
migrations
work
so
feel
free
to
leverage
him.
If
you
need
someone
who
will
hopefully
have
context
going
forward
and
also
don't
forget
that
all
of
us
are
qualified,
back-end
reviewers
so
don't
be
afraid
to
assign
first
round
reviews
out
to
one
of
us.
C
B
So
this
is
closed,
but
there's
a
new
issue
that
I
didn't
add
the
right
labels
to,
but
I'll
do
that
afterwards.
So
we
have
defined
targets
and
we're
meeting
with
I'm,
I'm
gonna
go
to
the
development
team
staff
meeting
today
and
we're
gonna
present
these
to
the
other
directors
and
so
hopefully
for
next
quarter.
People
will
start
adding
a
bunch
more
reviewers
and
that'll
take
some
of
their
reviewer
load
off.
So
that's.
B
Not
in
not
as
relates
exactly
to
this
one,
I
think
the
so
we
haven't
included
local
as
an
option,
because
it's
not
ready
yet.
That
said,
I
planned
on
scheduling
us
to
try
and
add
the
local
flag
in
the
next
milestone,
hoping
that
we
could
try
and
wrap
up
batch
background
migrations,
the
mvp
first
and
then
so
next
milestone.
E
B
B
E
E
B
E
B
E
B
All
right
hiring
update,
so
we
are
now
hiring
next
quarter,
which
means
that
I'm
spending
a
lot
of
time,
trolling,
linkedin
and
doing
other
things.
If
you're
interested
in
sharing
something
to
your
network.
Let
me
know-
and
I
will
I
can
help
you
write-
that
or
feel
free
to
just
share
the
job
posting
or
the
video
from
our
recruiter
or
one
of
giannis's
videos
from
the
past
or
if
he
records
another
video,
so
hoping
to
find
a
couple
of
really
great
folks
to
come
and
join
us.
G
G
G
D
G
G
D
B
D
D
D
D
All
the
outstanding
migrations
set,
the
cons
set
the
migration
back
down
again
and
then
and
then
kick
it
all
off
again.
It's
it's
just
going
to
take
some
time.
It
is
what
it
is
that
has
now
been
running
since
the
weekend
before
last,
so
we're
looking
what
nine
days
or
something
the
two
tables
are:
130
million
rows
and
rounding
error
in
terms
of
the
events
table
being
slightly
larger.
D
D
D
D
D
D
D
I
only
really
care
about
the
database
state
data
and
that
sort
of
block
storage
I
mean
it
may
well
not
be
local
block
storage,
it
may
well
be
iscsi
or
or
or
something
I
don't
know
they.
They
clearly
have
some
kind
of
callback
nas.
So
I
don't
know
exactly
what
it's
on
blitz,
block,
storage
and
and
balance
the
probabilities
it's
going
to
be
similar.
I
would
guess,
and
and
certainly
yeah
they've
got,
the
table
sizes
are
in
the
order
of,
I
think
the
largest
one
was
33
gigabytes.
B
D
Well,
ideally,
ideally
it
would
be
yes,
but
unfortunately
it
can't
insert
into
the
push
events
table
because
the
trigger's
missing
so
the
the
trigger
that
updates
the
new
primary
key
is
missing
because
it
was
pulled
out
by
one
of
the
subsequent
migrations
and
so
every
record
insert
inserts
the
event
id
into
the
old
primary
key
and
tries
to
zero
into
the
into
the
field
for
the
new
primary
key.
That
fails
the
constraint,
because
there's
no
zero
record
in
the
events
table,
so
they
can't
insert
any
records
into
that
table
at
the
moment.
F
D
D
C
D
E
Check,
what's
the
difference
to
the
test
system,
then
did
I
hear
that
correctly
that
they
managed
to
run
that
migration
so
validating
this
constraint
within
like
one
minute
yeah,
and
it
takes
multiple
days
on
their
production
system
yeah
and
one
difference
that
we
identified
as
the
traffic
coming
in
so
on
production?
There
is
traffic
on
tests.
There
is
none.
Is
there
any
other
difference?
Do
we
know.
D
F
D
C
D
Yeah
so
I
mean,
I
think
I
think
the
state
of
vacuum
and
analyze
kind
of
sticks
out
at
me.
At
the
moment
I
mean
I
I
I
did
check
you
can't
want
to
explain,
alter
table,
but
I
guess
that
fundamentally
order
table
validate
constraint
is
doing
something
which
will
go
through
the
you
know.
It's
it's
gonna.
It's
gonna
cover
strategy,
different
strategies
for
doing
that,
and
it's
gonna
have
to
pick
one,
but
it
doesn't
look
like
you
can
expose
what
those
are.
F
G
G
D
D
F
One
way
you
could
see
what
it's
doing
is
we
could
run
some
stuff
over
pg
station
user
tables
to
see
like
where
is
it
actually
spending
most
of
its
disc
time
to
see
if
it's
chewing
at
a
table
or
not?
That
will
be
kind
of
complicated
if
they're
also
running
production
on
this
at
the
same
time,
but
maybe
they
could
take
a
couple
snapshots
with
it
running
and
then
turn
off
the
valley
constraint.
Take
a
couple
snapshots.
D
E
C
D
A
B
D
E
D
Yeah
yeah
I
mean
they're
talking
about
they
were
talking
about
using
ip
tables
to
firewall
off
gitlab,
so
that
the
analyzer
would
be
able
to
the
analyzer
vacuum
would
be
able
to
run
so.
Downtime
is
definitely
on
the
cards
and
and
yeah
and-
and
I
mean
the
migration,
if
you're
running
the
migration,
the
weight
tasks,
you
don't
need
sidekick
or
right
puma,
because
it's
self-contained,
so
we
could
just
shut
everything
down.