►
Description
This was for the purpose of validating the ability to upgrade and run PG 11 in the context of Geo with separate DB nodes. See the issue here https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4975
Unfortunately I was reusing a tracking database that was already on PG 11, so I plan to retest, but I think I caught most issues, and validated that this is possible. The tracking database upgrade is unlikely to introduce a serious problem since it doesn't involve breaking replication or anything like that.
A
All
right,
I
am
going
to
upgrade
to
Postgres
11
on
a
Geo
installation
that
has
separate
database
nodes
on
the
primary
and
separate
database
nodes
on
the
secondary
and
the
tracking
database
is
separate
from
the
read
replicas.
So
this
is
just
to
verify
that
we
have
the
ability
to
do
this
just
with
omnibus,
as
is
without
you,
know,
custom
post,
Chris,
commands
or
manually
doing
it.
A
A
A
B
B
A
A
A
B
A
A
A
Right
Postgres
eleven
is
not
a
default
yet
so
we
need
to
specify
the
target
version
is
eleven
in
our
case,
but
the
purpose
of
this
is
to
validate
that.
It's
okay
for
us
to
make
the
default
PG
version
11,
which
would
make
this
command
automatically
target.
11
I,
believe
so
nothing
to
change
here.
But
for
our
tests
we
need
to
specify
the
target
version.
A
A
C
A
B
A
A
A
A
A
A
A
C
A
Like
it
is
okay
that
looks
like
things
are
working,
the
only
thing
we
tested
was
if
the
tracking
database
is
already
on
Postgres
alive
in,
but
the
other
two
databases
are
on
Postgres
ten
does
the
upgrade.
It
appears.
I'm
gonna
run
QA
against
it,
but
I
might
I
might
do
this
test
again,
where
we
do
the
tracking
database
upgrade
at
the
same
time,.