Logical replication of large objects

[Andreas Joseph Krogh]

I started this thread 5 years ago: 
https://www.postgresql.org/message-id/flat/7c70d9bd-76fc-70fa-cfec-14f00a4a49c3%40matrix.gatewaynet.com#15cbf1c82be9341e551e60e287264380
 




We'd be willing to help funding development needed to support Large Object 
logical replication.

Anyone interested?






--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andr...@visena.com 
www.visena.com 
 

Re: Why password authentication failed for user "postgres"?

[Frank Finner]

On 2022-06-04 00:32, BeginnerC wrote:

Hello everyone,
I am a newbie to the postgres,when I use the psql to connect to the 
postgres,a error message printed:

These command list like this:

psql -U postgres
Password for user postgres:postgres
*postgreSQL: password authentication failed for user "postgres"*
*
*
How to solve this problem?
Thanks in advance!


 * Which OS are you working on?
 * Can you show us your pg_hba.conf?

If you use -U with psql, the connection must not try to use method 
"peer" (which means "use the system user with this name", but also means 
"You must be logged in with the system user corresponding to the 
postgresql user"), but some kind of authorization, like md5, and use it 
with IP address. This might be difficult for the user postgres, who 
often has no password set in the database. If you really need to connect 
with user postgres and some password, you can set one using the method 
described by Reid Thompson.


Regards,

Frank




OpenPGP_0xE5418B2366C33EE6.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: Why password authentication failed for user "postgres"?

[David G. Johnston]

On Sun, Jun 5, 2022 at 4:06 PM Frank Finner  wrote:

> If you use -U with psql, the connection must not try to use method "peer"
> (which means "use the system user with this name", but also means "You must
> be logged in with the system user corresponding to the postgresql user"),
> but some kind of authorization, like md5, and use it with IP address.
>
This is simply wrong (though I suppose only in a corner case).  You must
connect via socket but peer authentication can still work.  In particular,
so long as the value specified for "-U" is your operating system user name
the connection will work just the same as if you didn't specify -U at all
and instead relied on the psql default behavior of using your operating
system user name for the value of user.  In short, the server only knows
what value "user" has as part of the connection string - it has no
knowledge of how that value became set.  However, it can prove that the
socket connection being requested is owned by a particular user.

I think (going from memory at the moment) you can get the main exception to
this rule via usage of pg_ident.conf (i.e., be logged in as "osuser" and
supply "-U postgres"; peer auth will work so long as osuser is mapped to
postgres and you connect via the socket (i.e., local, not host).

David J.