►
From YouTube: 2020 06 29 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
Monday
everybody
right
before
get
it
too
far
to
the
meaning,
so
I've
heard
different
preferences
from
different
team
meetings
on
how
people
their
preferences
on
whether
or
not
I
should
share
the
agenda
or
turn
it
off
and
just
see
each
other's
faces
instead,
so
there
any
preference
here.
Would
you
rather
me
share
the
screen
and
take
notes?
Everybody
can
see
or
turn
it
off,
so
you
can
track
on
your
own
and
get
the
close-up
of
everybody.
B
A
There
was
a
topic
that
came
up
last
week.
That
andre
has
pointed
me
to
that
there
was
some
miscommunication
about
the
PG
11
upgraded
and
how
it
affected
GD
k,
GC,
k,
GC
kane
came
up
this
morning,
so
I
can't
remember
who
put
this
line
item
in
here,
but
I
put
in
future
planning
issue
for
that,
so
that
we
make
sure
that
we
learned
from
this
on
how
we
can
get
better
at
communicating
out
the
major
upgrades,
because
we're
gonna
be
doing
this
annually
right.
A
We're
gonna
get
into
a
cadence
where,
where
you
are
following
the
Postgres
upgrades
with
our
major
upgrades,
I'm
still
want
to
make
sure
that
what
have
we
missed
this
time,
we
don't
miss
next
time
and
just
continue
to
iterate
and
get
better
so
I
created
an
issue
just
continue
to
take
notes
on
areas
that
we
may
have
missed
or
can
improve
on
in
the
end,
make
sure
it
gets
incorporated
to
the
next
upgrade.
So
any
questions
on
that
I.
B
Wasn't
sure,
like
obviously,
we've
missed
the
GDK
side
and
she's
okay
and
perhaps
even
other
projects
that
we
don't
even
know
of
so
it's
it's
a
sort
of
a
wide
area
have
to
consider
for
that
I.
Guess
it's
on
us
to
find
those
projects
and
communicate.
But
perhaps
not
you
know
it's
not
on
us
to
fix
all
those
projects
or
to
it's
more
about
the
organizational
aspect.
The
Padre
yeah.
A
Absolutely
yeah
and
working
with
product
right
I
think
Josh
should
have
a
big
area
of
responsibility
here
to
make
sure
that
he
disseminates
amongst
product
management.
Ok,
we
have
these
plans
that
upgrade
a
feature
that
you're
all
dependent
on
and
those
teams
should
look
into
how
all
impact
them
and
make
sure
that
they
understand
and
support
those
upgrade
paths.
So
there's
still
some
things
to
learn
about
the
coordination
piece
of
it.
A
C
Hello,
Craig,
hello,
everyone,
yes,
I,
would
like
to
share
with
you
guys.
I
mean
topics
that
we
are
working
on.
Infrastructure,
side
and
initiatives
are
basically
and
now
at
the
moment,
creating
more
on
books
to
every
supporters.
We
don't
call
executives
from
tasks
as
this
time
we're
trying
to
execute
with
the
support
of
a
sorry
they
repack
of
some
indexes
and
tables.
Then
some
things
we
are
working
depending
on
the
cycles
and
time
on
the
logical
application
and
able
to
exams
I
did
some
dashboards
from
saturation
analysis
that
are
now
part
of
the
graph.
C
Anna
I
will
try
to
implement
some
stuff.
Some
points
with
the
dashboards
of
saturation
from
Andrew
Terra,
more
generic
is
one
and
then
more
projects
that
we
are
thinking
about
like
to
improve
the
database
field,
overs
with
PE
pre-warm
and
as
well,
to
make
pity
badges
to
generate
reports
based
on
the
logs
from
the
database
to
code
to
bring
this
information
more
easy
for
everyone.
When
we
have
instant,
so
we
want
to
analyze
the
performance
of
queries
on
the
database,
all
right,
of
course,
all
of
them
I
will
not
manage
to
finish
in
this
quarter.
C
C
Perhaps
we
don't
need
them
or
I,
don't
know
if
we
can
try
to
look
this
with
them
with
the
team
from
with
a
development
team
for
how
long
we
need
to
keep
the
stages
of
the
builds
in
this
database,
because
maybe
we
could
have
a
second
datastore
data
store
and
lock
this
we
move
the
partitions
through
another
to
destroy
than
all
right.
Sandra
do
this
for
our
live
database.
Yes,
yeah.
B
Did
you
see
the
epic
and
idea
tracks
whistling
that
there
is
actually
support
for
CIA
retention,
so
basically
dropping
that
data?
After
is
that
one?
And
apparently
we
already
support
that,
and
the
question
is
just
if
we
can
enable
that
on
get
a
comm
I,
think
that
would
help
us
greatly
if
we
can
get
rid
of
the
very
old
data,
so
that
is
already
available.
It's
just
a
matter
of
enabling
it
we're
making
the
decision
to
enable
it.
C
B
D
D
Just
to
check
the
obvious
thing,
but
that
sham
normal
I
don't
need
to
spend
some
time
getting
my
head
around
how
the
tables
structured
and
how
statistics
really
work
so
I
mean
jumbly.
It
could
be
that
the
projects
table
doesn't
have
accurate
statistics
or
something
or
something
that
just
happens
to
be
big
in
the
50k
environment
and
I.
D
Don't
really
know
where
to
start,
but
it
would
be
really
useful
to
have
some
documented
steps
from
a
support
perspective
for
when
this
happens,
because
at
the
moment
we've
been
only
encountering
it
when
customers
have
no
statistics
at
all,
usually
because
of
an
upgrade,
but
if
they
did
get
anything
more
interesting
than
that
Madrid
struggle
somewhat
so
yeah.
My
ask
is
whether
whether
if
we
we
collaborated
with
we're
looking
to
grants
issue
whether
or
not
we
can
collaborate
or
not
in
some
way
and
I
can
have
a
takeaway
to
do
some
dogs.
A
B
Have
to
look
into
the
updates,
but
the
the
last
observation
that
we
made
was
that
the
back
room
was
perhaps
missing,
where
we
didn't
didn't
run
that
right
after
after
introducing
that
seemed
to
drop
down
and
the
latest
update
from
Graham
sounded
like
it
was
coming
back.
Even
though
we're
not
turning
the
back
room,
yeah
I,
don't
have
to
details,
we
do
have
to
run
books
for
good
luck.
Perhaps.
C
D
No
I
don't
think
we
do
so
when
omnibus
doesn't
upgrade,
it
includes
an
analyze.
At
the
end,
there
was
a
bar
recently
around
that
failing
and
the
output
not
being
captured.
So
there's
been
some
improvements
from
that
where
customers
are
using
omnibuses
Postgres,
it's
relying
on
them
knowing
to
do
that
fundamentally
or
forms
on
or
following
any
ws
is
footnotes.
D
A
I've
added
it
to
our
DB
office
hours
tomorrow,
so
we
have
the
team
office
hours
tomorrow
at
6:00
a.m.
Pacific
time,
along
with
issue
that
Yanis
brought
up
to
talk
about
tomorrow.
So
we
can
comment
async
and
then
we
can
discuss
more
tomorrow
so
that
we
can
get
through
this
weekly
agenda
today.
Thanks
for
bringing
it
to
our
attention,
then
we'll
definitely
follow
up
on
it.
Cool.
E
E
The
migration
helpers
are
were
merged.
That
part
is
ready
on
my
end,
I'm
working
on
the
post
migration,
for
which
I
guess
isn't
even
mine,
calls
for
last
week
a
select
one
issue:
I
haven't
really
looked
at
too
much
in
the
the
tracking
in
Sigurd
add-in
cert
trigger
a
benchmark
is
I
was
working
on
that
on
Friday.
Probably
you
have
that
wrapped
up
today,
I
mean
I.
Have
it
written
I
just
need
to
collect
numbers
on
there?
The
server.
B
Product
analytics
that
one
shifts
or
the
database
migration
ships
yes
last
week
that
had
the
hash
hash
partitioning
strategy
included,
which
led
to
the
discovery
and
development
environment
so
I'm
following
up
today,
edit
the
warning
and
see
what
else
we
can
add
and
documentation,
I
hope
we
don't
have
to
revert
the
change,
I'm
hoping
it
goes
in
that
direction,
anyways
and
otherwise.
I'm
working
on
managing
those
expectations,
I'm
halfway
through
I,
hope
I
can
give
it
to
Patrick
tomorrow
for
first
thoughts.
A
You
know
this
URL
last
week,
so
we
didn't
have
goals
set
for
this
week.
So
for
this
week
we
do
have
the
retro
4:13
one
laughs,
retro.
We
got
everything
in
at
the
last
minute,
like
the
day
before,
which
puts
a
lot
of
pressure
in
this
case
on
Wayne,
to
get
everything
organized.
So,
let's
get
our
retro
in
much
earlier
to
make
his
like.
Whoever
is
actually
facilitating
this
time,
make
their
life
a
little
bit
easier.
A
We
are
about
halfway
through
the
milestone,
so
I
want
to
look
at
what
was
unassigned
and
see
if
there's
anything
that
we
just
know
we're
not
going
to
get
to,
and
we
should
just
move
over
now
or
if
there
are
things
that
folks
are
working
on
which
just
haven't
been
assigned
her,
so
so
only
five
sticks.
Okay,
so
is
anybody
working
on
the
automatically
indexing
I?
Think.
B
A
A
B
We
don't
have
a
working
model
at
the
moment
because
we
don't
have
you
haven't
finished
the
audit
events
migration.
Yet
but,
interestingly,
the
product
analytics,
Mr,
D
C,
is
going
to
add
a
model
for
that
soon,
maybe
this
week,
and
maybe
we
can
even
use
it
for
for
implementing
some
helpers
around
that
to
you
know,
make
sure
that
in
the
products
analytics
feature,
we
always
use
positioning
key
so
that
might
work
out
I,
don't
think
it's
a
high
priority.
I.
E
Want
to
wrap
up
the
finalized
partitioning
migration,
help
her
the
post
migration
and
there's
a
few
changes
that
came
out
of
that
that
there's
M
ours
that
are
being
reviewed
right
now
and
the
other
one
is
we
were
supposed
to
originally
this
morning,
deploy
the
issue.
That's
been
out
there
for
a
while
for
this
conflict-free
schema
version
handling.
E
B
C
A
So
one
thing
we
need
to
find
the
thing
you
sow
on
your
issues
that
you're
working
on,
if
you
are
going
to
ship
them
in
this
milestone,
please
mark
them
as
deliverable.
There's
a
new
initiative
out
there
for
say,
do
ratio.
So
when
we're
working
in
the
milestone,
the
things
that
we
say
we're
going
to
do
and
what
we
actually
do,
they're
trying
to
measure
them
to
see
what
our
ratio
is,
the
way
we
work
or
a
little
more
Kanban
style.
A
We
pick
things
up
as
we
go
along,
but
it's
still
a
good
exercise
for
us
to
go
through
and
Mark
things
as
deliverable
through
the
milestone.
If
we
feel
we
are
going
to
ship
them
in
the
same
milestone,
and
then
we
can
review
things
that
slip
over
a
milestone.
So
if
you
pick
something
up
in
the
last
week
of
the
milestone,
you
know
it's
not
going
to
make
it
just
don't
mark
it
as
deliverable
and
then
we
can
review
it
for
the
next
milestone.
A
B
Was
a
suggestion
to
add
another
release
post
to
make
sure
that
the
posters
11
upgrade
is
heard
now
that
we
have
this
breaking
migration?
That's
something
we
should
be
doing
like
I
mean
we've
sort
of
publicly
announced.
That's
not!
Oh!
It's
going
to
need
to
produce
11,
put
an
emphasis
on
that
as
well
again,
I.
A
I
think
it's
a
good
idea.
I
think
it
should
probably
be
a
targeted
release
post,
because
our
last
several
release
posters
have
had
the
deprecation
warnings
at
the
bottom
of
the
page.
So
it
seems
like
that
would
just
kind
of
fall
into
the
void.
If
we
say
hey,
it's
you
know,
PG
11
is
required,
I
think
if
we
make
it
specific
to
the
issues
that
we've
seen
like
hey,
we
know
there's
an
issue
with
GVK.