I am not an expert but I will try to explain.
replication user has access to WAL stream, bypassing any revoked
permission on any database.
I think that is the reason to force a specific user with specific
permissions for replicationyou don't want user x reading WAL stream
while you don't
On June 7, 2011 04:38:16 PM owen marinas wrote:
> Thx, Merci, Gracias Rodrigo
> it worked indeed, Im wondering why replication is not included in "All"
>
Probably because it gives access to all the data being written to the
database.
--
Obama has now fired more cruise missiles than all other N
Thx, Merci, Gracias Rodrigo
it worked indeed, Im wondering why replication is not included in "All"
regards
Owen
On Tue, Jun 7, 2011 at 2:40 PM, Rodrigo Gonzalez
wrote:
> On 06/07/2011 03:05 PM, Owen Marinas wrote:
>>
>> Added the lines in the Master
>> root@ip-172-19-1-37:~# cat /etc/postgresq
On 06/07/2011 03:05 PM, Owen Marinas wrote:
Added the lines in the Master
root@ip-172-19-1-37:~# cat /etc/postgresql/9.0/main/pg_hba.conf |grep trust
host all postgres 172.19.1.101/32 trust
You need in pg_hba.conf
hostreplication repuser 172.19.1.101/32 md5
Database
Hi,
I configured replication in 2 AWS instances.
I have shell scripts to dynamically configure the Ips after the
instances are UP.
the Postgres versions are the same in master& slave, also the
architecture of instances.
Added the lines in the Master
root@ip-172-19-1-37:~# cat /etc/postgresql
