Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pu70L-0000VD-6A for pgsql-general@arkaria.postgresql.org; Wed, 03 May 2023 07:34:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pu70K-0007x6-2F for pgsql-general@arkaria.postgresql.org; Wed, 03 May 2023 07:34:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pu70J-0007wx-OE for pgsql-general@lists.postgresql.org; Wed, 03 May 2023 07:34:23 +0000 Received: from mail-yw1-x1129.google.com ([2607:f8b0:4864:20::1129]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pu70D-000Iq1-66 for pgsql-general@lists.postgresql.org; Wed, 03 May 2023 07:34:23 +0000 Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-55a8019379fso24403097b3.0 for ; Wed, 03 May 2023 00:34:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683099255; x=1685691255; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=cEg+nw3FNXydlzOeNVqWPvNOrw/48xKJWTcNydoi1FM=; b=e+tPjwSsiedaQJoI4AAtsvjupahKbUIFSw3lfz/wVHFokIMQv1pNMSyq6pathoOnK7 GQ0FE+oXAW5I0z5lDGdNN6FnzrcBc310ix3bSk/N+07cGHWHOrb4WPDNYse6mPzbwGHl 30HY6ber90OsUeA2mJ990aAmZ57dlQrj7wGAZENT5Q+Yhp75OsN6AsFidk+dNKxPcuBR lrcSxxdXmwP2HRKB2/KsjES5rqJD36CftYx0nIAAPj+goH5CdCsBozAMCTR/C2cHvNhE kkBFXzKJUZ4KtTXt8gWDrFZ6LgJlIRISSkjYtCt/kNMGOixD1Vmliya9oYCvuBkDKncU wFlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683099255; x=1685691255; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=cEg+nw3FNXydlzOeNVqWPvNOrw/48xKJWTcNydoi1FM=; b=gWIZWQx5J8ysddhU1uI/cMaQw/hDZ7lPMsVgSVursazgJh4wCU+WG4dBWJcr8kXcQU S3dQmknfZ61DF0O0jxr4hzogJ9eEXn71QZJo8hjhTHT3IXBrNGmqEPu+pu8XZ/YDxHy3 8AEMReNHziSi80eLbAFXfunH4v0UcLDsYFy0UPeFs+aNTWX7FyeykAYzWiod2J6hyuSO xQdRBKIGcoZSTIR0V8RWtEMabpm2zJVVI45xVSnqMQvc0MWP8aB0VQzsJ6bLC6tdmYHV oKYa/iv8AWXWTSjcAbzMfo1Rd2yJZSiZ0UjoAx7ua7JkMa+yQx0uCJ7Ef5honDJJFc6Q eYVw== X-Gm-Message-State: AC+VfDzryZ6jSqRWLYWVC8QCMAja81GrYuCi+WocPRZIsVaS4sNHdZoT 0pZXgMimMPy3BBz+LO+8dwcRTluUCaE= X-Google-Smtp-Source: ACHHUZ5fB7p8ub0FMoEjsw1LO+YmQ5AvVhGwJSftHzxPpvL+Ha9vE+AMSm5+Yj0R2i9AWrXW6leoXQ== X-Received: by 2002:a0d:f486:0:b0:541:7e07:ed65 with SMTP id d128-20020a0df486000000b005417e07ed65mr17639894ywf.5.1683099255600; Wed, 03 May 2023 00:34:15 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:4591:da55:f616:329f? ([2600:1700:bd2c:b810:4591:da55:f616:329f]) by smtp.googlemail.com with ESMTPSA id w3-20020a814903000000b00559d1eabc3csm2982135ywa.79.2023.05.03.00.34.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 May 2023 00:34:15 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------Fg5sZ8rSy60lnKPCyyp9pxbj" Message-ID: <7604c2bc-b914-95e4-a969-b85bbcdded0d@gmail.com> Date: Wed, 3 May 2023 02:34:14 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Can one user login in multile machine? Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Fg5sZ8rSy60lnKPCyyp9pxbj Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/3/23 01:23, Wen Yi wrote: > Hi team, > can I use same user's information login in multile machines when connect > to the postgres? Your question is a bit ambiguous, since: 1. "login in (to) multiple machines" typically refers logging in to the OS, and that has nothing to do with postgresql, and 2. a specific postgresql database can only be on one server. Having said that... when doing streaming replication, role details (including authentication credentials) will be automatically replicated to the secondary just like every other bit of "the postgres". -- Born in Arizona, moved to Babylonia. --------------Fg5sZ8rSy60lnKPCyyp9pxbj Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 5/3/23 01:23, Wen Yi wrote:
Hi team,
can I use same user's information login in multile machines when connect to the postgres?

Your question is a bit ambiguous, since:
1. "login in (to) multiple machines" typically refers logging in to the OS, and that has nothing to do with postgresql, and
2. a specific postgresql database can only be on one server.

Having said that... when doing streaming replication, role details (including authentication credentials) will be automatically replicated to the secondary just like every other bit of "the postgres".

--
Born in Arizona, moved to Babylonia.
--------------Fg5sZ8rSy60lnKPCyyp9pxbj--