On Thu, 2022-05-19 at 13:18 +0900, 菊池祐 wrote:
> I executed the pg_basebackup command to set up a replication configuration in
> postgresql,
> but the following message appears and replication didn’t complete.
>
> 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 kB
> (100%), 27
Hi,I executed the pg_basebackup command to set up a replication configuration in postgresql, but the following message appears and replication didn’t complete.2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 kB (100%), 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/126
Dominique Devienne writes:
> AFAIK, it’s not psql that does this though, it’s libpq the official client
> api.
> And the fact libpq has no way to surface that info seems like an important
> oversight.
PQconninfo() will show you all the option values in use by a connection
object. It's true that
Hi, folks;
I’m in the process of testing PG v12.7 hot streaming standby’s in async mode,
and specifically in the area of reliable switchover and switchback operations.
I have created test primary’s and standby’s successfully with pg_ctl initdb and
pg_basebackup respectively. I can switch over/s
On 5/18/22 14:59, Dominique Devienne wrote:
AFAIK, it’s not psql that does this though, it’s libpq the official
client api.
And the fact libpq has no way to surface that info seems like an
important oversight.
Not all clients use libpq e.g. the Postgres JDBC driver. It just uses
the P
On Wed, May 18, 2022 at 5:43 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wed, May 18, 2022 at 3:08 AM Dominique Devienne
> wrote:
>
>> Once connected, can I find out all aspects of the connection string?
>> Or where they came from, like a pgpass.conf or service file?
>>
>> How
On Wednesday, May 18, 2022, Koen De Groote wrote:
> The documentation here: https://www.postgresql.org/
> docs/11/continuous-archiving.html
>
> States:
>
> > It is advisable to test your proposed archive command to ensure that it
> indeed does not overwrite an existing file, *and that it returns
The documentation here:
https://www.postgresql.org/docs/11/continuous-archiving.html
States:
> It is advisable to test your proposed archive command to ensure that it
indeed does not overwrite an existing file, *and that it returns nonzero
status in this case*.
Why exactly is this?
Assuming a s
I've got a setup where archive_command will gzip the wal archive to a
directory that is itself an NFS mount.
When connection is gone or blocked, archive_command fails after the timeout
specified by the NFS mount, as expected. (for a soft mount. hard mount
hangs, as expected)
However, on restoring
On Wed, May 18, 2022 at 3:08 AM Dominique Devienne
wrote:
> Once connected, can I find out all aspects of the connection string?
> Or where they came from, like a pgpass.conf or service file?
>
> How to get the host, port, db name once connected?
> SHOW and pg_settings does not appear to be it, a
On Wed, May 18, 2022 at 12:07 PM Dominique Devienne wrote:
> LibPQ has various defaults for the host, user, and DB name.
> There's also the password file, the service file and service name.
> In the example below, I can connect with a "naked" psql invocation.
>
> Once connected, can I find out all
2022年5月18日(水) 23:07 Wiwwo Staff :
>
> Hi!
> i might be doing something wrong, but I cannot see what...
>
> Server is 14.3 (Debian 14.3-1.pgdg110+1)
> (at the time of writing, in Dockerfile FROM postgres:14)
>
> I have a 3 node cluster, starting with pg_red (172.26.0.2) as primary.
> I promote pg_gr
Hi!
i might be doing something wrong, but I cannot see what...
Server is 14.3 (Debian 14.3-1.pgdg110+1)
(at the time of writing, in Dockerfile FROM postgres:14)
I have a 3 node cluster, starting with pg_red (172.26.0.2) as primary.
I promote pg_green (172.26.0.4) as new primary, all other aligned
## Dominique Devienne (ddevie...@gmail.com):
> Once connected, can I find out all aspects of the connection string?
\conninfo in psql (pro tip: \? actually helps), "Connection Status
Functions" https://www.postgresql.org/docs/current/libpq-status.html
in libpq; and in a pinch you could find your
\conninfo will show you desired details
Regards,
Ganesh Korde.
On Wed, 18 May 2022, 3:38 pm Dominique Devienne,
wrote:
> LibPQ has various defaults for the host, user, and DB name.
> There's also the password file, the service file and service name.
> In the example below, I can connect with a
Hi Dominique,
you can use \conninfo in psql to show the database, user, host (or socket in my
example), and port:
ewie@desktop ~ $ psql test
Null display is "".
psql (14.3)
Type "help" for help.
test=# \conninfo
You are connected to database "test" as user "ewie" via socket in
"/run/postgresql
LibPQ has various defaults for the host, user, and DB name.
There's also the password file, the service file and service name.
In the example below, I can connect with a "naked" psql invocation.
Once connected, can I find out all aspects of the connection string?
Or where they came from, like a pg
17 matches
Mail list logo
