On Mon, 27 Apr 2020 at 17:52, Tom Lane wrote:
>
> Radu Radutiu writes:
> > Can you guide me how to debug postgresql crash?
>
> A stack trace would be pretty useful.
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
> regards, tom lane
Matthias Apitz writes:
> As the client seems to be waiting on the server and the server on the
> client... could it have been caused by this in /etc/hosts (what our IT
> department configured):
Doubt it. Your connection evidently got through (at least) the
authentication exchange, so basic data
Matthias Apitz writes:
> El día Montag, April 27, 2020 a las 08:40:04 -0400, Tom Lane escribió:
>> Can you get a stack trace from the connected backend?
> (gdb) bt
> #0 0x7fd567776000 in epoll_pwait () from /lib64/libc.so.6
> #1 0x0084476c in WaitEventSetWaitBlock ()
> #2 0x000
Hi Tom,
> On 27. Apr, 2020, at 15:13, Tom Lane wrote:
> [ shrug... ] When connecting via a Unix socket, psql does not have a
> relevant "hostname" to report, so it reports what it's got. You are
> ascribing a meaning to HOST that it does not have, never has had, and
> never can have in this cas
As the client seems to be waiting on the server and the server on the
client... could it have been caused by this in /etc/hosts (what our IT
department configured):
/etc/hosts:
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
i.e. the
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
>> On 27. Apr, 2020, at 14:20, Tom Lane wrote:
>> AFAICS, psql is behaving as documented. Why are you trying to override
>> HOST like that, instead of just using some other variable?
> I could but
> a) HOST is HOST and should not point to a socket director
El día Montag, April 27, 2020 a las 08:40:04 -0400, Tom Lane escribió:
> Matthias Apitz writes:
> > I encounter from time to time that one of our ESQL/C clients hangs with
> > the details described below for ever, while accessing on startup a table
> > 'sisisinst' which has only some 50 rows, al
Hi Tom,
> On 27. Apr, 2020, at 14:20, Tom Lane wrote:
> AFAICS, psql is behaving as documented. Why are you trying to override
> HOST like that, instead of just using some other variable?
I could but
a) HOST is HOST and should not point to a socket directory. A socket directory
is not a HOST.
Matthias Apitz writes:
> I encounter from time to time that one of our ESQL/C clients hangs with
> the details described below for ever, while accessing on startup a table
> 'sisisinst' which has only some 50 rows, all of CHAR columns. Other ESQL/C
> clients
> start up fine (they all check this
Radu Radutiu writes:
> Can you guide me how to debug postgresql crash?
A stack trace would be pretty useful.
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
Hello,
I encounter from time to time that one of our ESQL/C clients hangs with
the details described below for ever, while accessing on startup a table
'sisisinst' which has only some 50 rows, all of CHAR columns. Other ESQL/C
clients
start up fine (they all check this table 'sisisinst' on sta
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
> the use of :HOST in psql containing the socket directory for local
> connections is pretty useless for us, so we set it to the hostname in a
> global psqlrc file:
> \set HOST `hostname -s`
> This works great when invoking psql on the command line. But if I
Hello!
This address is for reporting issues with the PostgreSQL website, it is not
a help desk. For general support questions, please see
https://www.postgresql.org/support/ - in particular, consider the
pgsql-general public mailinglist, as you seem to have already done, and
received a reply there
Hi,
Can you guide me how to debug postgresql crash?
I have a development VM (kvm) running Centos 8.1(up to date with all
patches, kernel 4.18.0-147.8.1.el8_1.x86_64,
postgresql12-server-12.2-2PGDG.rhel8.x86_64 ) with a very large partitioned
table (few hundred GBs) . Creating an index on partition
Hi,
the use of :HOST in psql containing the socket directory for local connections
is pretty useless for us, so we set it to the hostname in a global psqlrc file:
\set HOST `hostname -s`
This works great when invoking psql on the command line. But if I perform a \c
to connect to a different da
On Monday, April 27, 2020, David G. Johnston
wrote:.
>
>
> Are there plans to add comprehensive schema change detection abilities via
>> logical replication ? either by embedding more information into pgoutput or
>> perhaps by embedding the schema DDLs ?
>>
>
> You could search the mailing list ar
Please don’t top-post.
On Monday, April 27, 2020, Andreas Andreakis
wrote:
> Thx for replying David.
>
> According to https://www.postgresql.org/docs/10/protocol-logicalrep-
> message-formats.html it looks like certain schema information is embedded
> via pgoutput such as column names and types.
Thx for replying David.
According to
https://www.postgresql.org/docs/10/protocol-logicalrep-message-formats.html it
looks like certain schema information is embedded via pgoutput such as
column names and types. However, if a new column name appears and a
previous not, then it is currently not poss
18 matches
Mail list logo
