## PegoraroF10 (mar...@f10.com.br):
> How can I hide that info from users which are connected to my replica server
https://www.postgresql.org/docs/current/catalog-pg-subscription.html
Access to the column subconninfo is revoked from normal users, because
it could contain plain-text passwords.
Paul A Jungwirth writes:
> I'm reading the docs about the Postgres Rule system here:
> https://www.postgresql.org/docs/12/rules-views.html
> That page says:
>> It turns out that the planner will collapse this tree into a two-level query
>> tree: the bottommost SELECT commands will be “pulled up”
Hello,
I'm reading the docs about the Postgres Rule system here:
https://www.postgresql.org/docs/12/rules-views.html
That page says:
> It turns out that the planner will collapse this tree into a two-level query
> tree: the bottommost SELECT commands will be “pulled up” into the middle
> SELE
Am 11.11.19 um 14:26 schrieb PegoraroF10:
How can I hide that info from users which are connected to my replica
server
you can use a .pgpass - file, see the documentation.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
We use replication with publication/subsctription. It´s ok, works fine.
But if I go to my replica server and do select * from pg_subscription
on field subconninfo I have all properties to connect. host, port, user,
password and dbname, all these info are available.
Documentation says user for repl
Hello.
I beg for the community ideas on how to do in the best way.
I use centrally storing syslog messages in Postgres. All devices send syslog messages to a server (or could be several in fault tolerance) which use
rsyslog to store the logs in the DB (currently I'm using mysql and postgre stor
Hello,
I am trying to setup barman for my test environment with the following steps
but I m not able to start the backup. Please advice !
Postgres 11.2 streaming replication on docker container , Centos
Server A : pg1 (primary)
Server B : pg2 (Standby)
I am using pg2 as a Barman server. Barm