Thanks! The steps I would recommend in this case:
- find a setting with which one can connect via `psql` - within psql, execute `\conninfo\ - use those settings to configure wal-e via env variables In my case, PGHOST='localhost' did not work, one had to set it to a unix socket file Am Di., 29. Jan. 2019 um 22:12 Uhr schrieb Daniel Farina <[email protected]>: > > > On Fri, Jan 25, 2019 at 6:31 AM Johannes Lüdke < > [email protected]> wrote: > >> Hi, >> >> I am setting up wal-e on a production server. My local proof of concept >> worked well, but now I get an >> >> ``` >> FATAL: Ident authentication failed for user "postgres" (SQLSTATE 28000) >> ``` >> > > It means that, for whatever reason, the defaults (which tend to rely on > unix sockets and peer authentication, as wal-e is conveniently run as the > postgres unix user by default), do not work for you. > > >> What is the recommended way to fix this? Can I configure which >> user/password wal-e uses to connect to the db? >> > > If you can't make the defaults work for some reason (I think you should > justify to yourself why that may be, and check pg_hba.conf), you have > control over credentials via libpq environment variables. > https://www.postgresql.org/docs/current/libpq-envars.html > -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
