Date: Mon, 4 Feb 2019 08:33:49 -0700 (MST)
From: PegoraroF10 <marcos@f10.com.br>
To: pgsql-general@postgresql.org
Message-ID: <1549294429092-0.post@n3.nabble.com>
In-Reply-To: <7719c8bd-2e98-8a67-d01d-3b111e8d669c@aklaver.com>
References: <1549209182255-0.post@n3.nabble.com>
 <37bc715f-12e2-84ac-6492-88d7b6306777@aklaver.com>
 <1549211574297-0.post@n3.nabble.com>
 <0689b9bcac79f7f5e76ed69dd4baea012d6a3d33.camel@gmail.com>
 <1549278827534-0.post@n3.nabble.com>
 <7719c8bd-2e98-8a67-d01d-3b111e8d669c@aklaver.com>
Subject: Re: Server goes to Recovery Mode when run a SQL
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

About replication ... Logical Replication with CREATE
PUBLICATION/SUBSCRIPTION.

Yes, some DDL commands were ran on that server but none of them were relate=
d
with that select.
Let me explain better. We have a single server with a single database on it=
.
Each customer has its own schema and connects to it to work exclusively on
that schema. So, sometimes we add some customer or change something on an
old one. But this DDL change we could ran is not related with that schema w=
e
are talking. Schemas can have different structures but that schema which
puts my server on recovery mode was not changed.

Maybe something related happened some days ago. When we start a new custome=
r
we add a schema, put all their tables on it and it=C2=B4s ok. Our server ha=
s
today 90 schemas and each schema has 100 tables, resulting in 9000 tables.
Some days ago we added 5 new customers on same day, so we added 500 tables.
Then, when we did that some selects on system tables were very very slow an=
d
that was only solved when we did a REINDEX DATABASE. Even REINDEX SYSTEM di=
d
not solve. Is this problem related with recovery mode of my server ?


--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.ht=
ml