►
From YouTube: 2020 03 16 Database Team Meeting
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
A
Mrs
for
the
month
to
merge
them
ours,
mostly
because
we're
doing
so
much
investigative
work
right
now.
It's
fine,
there's,
a
bunch
that
are
written
out
there,
but
and
I
haven't
figured
out
the
difference
between
these
two
graphs.
Something
I
need
to
look
into
so
either
have
two
or
three
depending
on
where
you
look
at
it's
the
board.
Twelve
nine
there's
still
some
work
to
be
done
on
this
one,
there's
still
some
open,
Ammar
work
that
andreas
is
getting
to
I,
know,
there's
a
lot
of
updates
on
that
one.
A
A
B
Yeah
that
actually
I
meant
to
pull
into
the
Kern
yeah
right
yeah,
that's
what
I
started
working
out
in
Friday
I
might
need
to
talk
to
Andreas
cuz
I.
The
way
the
discs
are
set
up
on
that
machine.
I'm,
not
sure
I'm
gonna
have
this
space
that
I
need
and
I
don't
have
the
access
to
do
that,
but
that
was
what
I
had
been
working
on
Friday.
You
know:
okay,.
A
And
then
we
have
some
other
future
looking
issues,
so
this
one
was
set
a
while
ago.
So
once
we
had,
he
set
pagination
working.
We
were
gonna,
set
some
limits
for
offset
pagination
so
that
we
don't
see
those
exponential
performance
degradation
as
you
get
further
along
an
offset
pagination
you'll
see
if
that
still
makes
sense
for
this
mouse
time,
we'll
leave
it
for
now.
A
B
Yeah
good
question
I
think
there
was
maybe
a
few
outstanding
questions
on
the
on
that
write-up
that
he
had
written
about.
Maybe
if
a
couple
places
we
wanted
to
check
and
make
sure
that
wouldn't
cause
like
a
performance
degradation
in
other
instances,
but
I
think
you
know
pending
that
I
think
it
would
be
something
that
we
would
want
to
move
forward
with.
A
Yeah
I'll
have
to
time
that
with
the
rollout
in
production
right
so
we'll
have
to
keep
it
local
until
it's
actually
out
on
comm
and
available
Postgres.
Eleven,
no
and
that's
still
being
targeted
for
early
April,
haven't
heard
anything
that
would
conflict
with.
That
sounds
like
anything,
there's
no
running
his
schedule
and
so
I.
A
Was
gonna
get
some
feedback
on
this
one,
so
I
updated.
The
mr2
describe
the
sharding
working
group
with
some
of
those
clarifications
that
we've
talked
about
in
this
weekly,
sync
that
we
have
and
some
of
the
discussions
we've
had
them
database
to
you.
So
I
called
out
our
development
plan,
so
building
charting
on
top
of
partitioning.
A
So
first
approach
is
to
deliver
the
MVC
implementation
and
then
that
will
better
inform
our
charting
approach,
which
is
something
we
talked
about
before,
calling
out
some
of
the
caveats.
So
there's
some
discussion
and
other
channels
that
were
working
on
data
isolation
with
sharding
and
I
wanted
to
call
out
that
we
are
exploring
data,
isolation
per
tenant
and
then
I
know
cockroaches
been
mentioned,
but
we're
calling
it
out
as
not
a
viable
option
at
this
point
in
time.
We're
not
doing
any
further
investigation
in
the
cockroach
and
then
called
out
some
of
the
dependencies.
A
So
infrastructure
rolling
out
closed
grass,
11
deploying
an
NBC
partitioning,
but
that's
dependent
on
the
first
step,
and
then
sharding
strategy
is
going
to
be
dependent
on
NBC.
So
there
are
there
any
other
high
points
they
may
have
missed.
On
this,
one,
like
Pat,
you're,
probably
closest
to
it
who's
on
the
call.
B
Think
they're
shorting
strategy
does
depend
somewhat
on
the
partitioning,
but
I
think
it
could
also
be
I
mean
it
I
think
it's
also
gonna
be
sort
of
its
own
thing
and
it's
still
sort
of
up
in
the
air,
because
I
don't
know
that
we
know
enough
about
the
solution
that
we're
picking
like
if
we
do
situs
I
think
it
would
follow
pretty
in
line
with
what
we're
doing
for
partitioning.
But
if,
for
some
reason
it
doesn't
meet
the
needs
that
the
business
is
looking
for,
then
I
think
it's
might
be
an
alternative
approach.