On Fri, 2019-09-27 at 11:10 +0530, Amarendra Konda wrote:
> As part of vacuum tuning, We have set the below set of parameters.
>
> > select relname,reloptions, pg_namespace.nspname from pg_class join
> pg_namespace on pg_namespace.oid=pg_class.relnamespace where relname
> IN('process_instance') a
Hi,
As part of vacuum tuning, We have set the below set of parameters.
*> select relname,reloptions, pg_namespace.nspname from pg_class join
pg_namespace on pg_namespace.oid=pg_class.relnamespace where relname
IN('process_instance') and pg_namespace.nspname='public'; relname|
reloptio
Hi Fan Liu,
I am able to make the connection to the Postgres database created in docker
container via psql from postgres10 client but not able to connect through
pg_isready.
psql -c 'select count (*) from pg_stat_activity' -h localhost -p 5432 -U
postgres -W
Password for user postgres:
count
-
Edilmar Alves writes:
> I use PG 11.5 into CentOS6 server, with 50 schemas, exactly equals in
> tables structure, and more than 400 tables/schema. Then, there is more
> than 2 tables.
Possibly you should rethink that design, but ...
> I changed the original PG view like said in the above t
Hi,
I use PG 11.5 into CentOS6 server, with 50 schemas, exactly equals in
tables structure, and more than 400 tables/schema. Then, there is more
than 2 tables.
I found the discussion in pgsql-general thread:
https://www.postgresql.org/message-id/flat/11566.1558463253%40sss.pgh.pa.us#ec14
Hi
čt 26. 9. 2019 v 9:55 odesílatel Joao Junior napsal:
> Hi,
> Is this necessary to run analyze on a slave using streaming replication
> after promotion??
>
No - column statistics are come from master - and are persistent - promote
change nothing.
Pavel
Hi,
Is this necessary to run analyze on a slave using streaming replication
after promotion??
