Hot answers tagged

3

Point 2, can be addressed by using AWS RDS to back up data for you. Otherwise, you manually need to create a snapshot of your EC2 instance but this involved a tiny bit of downtime and will cost money to store on S3. Point 1, just restore the database Either way, you want a high level of functionality that you don't want to pay for, so our options for ...


3

how any vendor can reliably ensure storage throughput (which is critical for DW performance) without creating a configuration bottleneck? By hiring really smart people to design their back-end systems. Why do we still talk about 'shared nothing' when every single cloud supplier uses virtualization and therefore shared storage? Shared ...


2

Execution plans: OBVIOUSLY. As does restarting the server - these are kept in memory and generated on demand. Which also means you never collected them over the years. Unless you have a never patched system which would be a much bigger problem. Statistics: no, those are actually objects in the database, so they transfer. Here you also did NOT collect them ...


1

Agreed -- db mirroring would be highly unlikely in this situation since it works best if it's persistent and would need manual intervention every time you turned your desktop system on. Snapshot Replication is the only realistic option in the replication world, and there's no benefit gained over using a simple database backup and restore or AWS snapshot.


1

Read the Friendly Manual: http://www.postgresql.org/docs/9.5/static/auth-methods.html You probably want to use https://github.com/larskanis/pg-ldap-sync to sync your LDAP users and groups to PostgreSQL


1

Thanks everyone, I just made a change in /var/lib/pgsql/9.4/data/pg_hba.conf with : local all all ldap ldapserver=ldap.server ldapport=389 ldaptls=0 ldapprefix="uid=" ldapsuffix=",ou=People,dc=domain,dc=com" And the authentication works!



Only top voted, non community-wiki answers of a minimum length are eligible