El día lunes, abril 26, 2021 a las 07:38:40a. m. +0200, Matthias Apitz escribió:
> Having solved this issue, one last question: Is there any good way for a
> C-written or ESQL/C-written client to get the local port number or even
> the PID of the PostgreSQL server process on the other end of the
>
El día domingo, abril 25, 2021 a las 01:54:49p. m. +0200, Matthias Apitz
escribió:
...
> # select * from pg_stat_activity where client_port = 52288;
>
> datid | datname | pid | leader_pid | usesysid | usename |
> application_name | client_addr | client_hostname | client_port
El día domingo, abril 25, 2021 a las 08:05:21p. m. +0200, Karsten Hilbert
escribió:
> > > > The serverlog has around this time (sorry for German):
> > > >
> > > > 2021-04-23 05:55:23.591 CEST [2317] LOG: unvollständige Message vom
> > > > Client
>
> "incomplete message from client"
>
>
Karsten Hilbert writes:
> Am Sun, Apr 25, 2021 at 01:21:25PM -0400 schrieb Tom Lane:
>> Still, the apparent message length is then "RP-2" (0x52502d32)
>> which is bigger than 1GB so I don't quite understand why you didn't
>> get an "out of memory" error.
> But he did, didn't he ?
Those log messa
Am Sun, Apr 25, 2021 at 01:21:25PM -0400 schrieb Tom Lane:
> > 10:57:16.051326 IP 127.0.0.1.52288 > 127.0.0.1.5432: Flags [P.], seq
> > 14280:14407, ack 120304, win 512, options [nop,nop,TS val 3424445708 ecr
> > 3424445708], length 127
> > 0x: 4500 00b3 b84e 4000 4006 83f4 7f00 000
Matthias Apitz writes:
> El día domingo, abril 25, 2021 a las 11:51:45a. m. -0400, Tom Lane escribió:
>> Hmph. So why wasn't this visible in the tcpdump trace?
> It was visible. That's why I detected it while looking up the TCP
> packages before the UPDATE:
> 10:57:16.051326 IP 127.0.0.1.52288
El día domingo, abril 25, 2021 a las 11:51:45a. m. -0400, Tom Lane escribió:
> Matthias Apitz writes:
> > At the end of the day, it turned out that out client caused the problem.
> > Because we were hunting some other issue, the client was logging some
> > message with fprintf(stderr, ...) but th
Matthias Apitz writes:
> At the end of the day, it turned out that out client caused the problem.
> Because we were hunting some other issue, the client was logging some
> message with fprintf(stderr, ...) but the fd=2 was not stderr, fd=2 was the
> connection to the socket of the PostgreSQL serve
El día domingo, abril 25, 2021 a las 01:54:49p. m. +0200, Matthias Apitz
escribió:
>From the collected data, I tend to say: this must be a bug in the Pos
> server...
>
At the end of the day, it turned out that out client caused the problem.
Because we were hunting some other issue, the client
El día viernes, abril 23, 2021 a las 11:32:02a. m. +0200, Matthias Apitz
escribió:
> El día viernes, abril 23, 2021 a las 10:48:24a. m. +0200, Laurenz Albe
> escribió:
>
> > > The serverlog has around this time (sorry for German):
> > >
> > > 2021-04-23 05:55:23.591 CEST [2317] LOG: unvollstä
El día viernes, abril 23, 2021 a las 10:48:24a. m. +0200, Laurenz Albe escribió:
> > The serverlog has around this time (sorry for German):
> >
> > 2021-04-23 05:55:23.591 CEST [2317] LOG: unvollständige Message vom Client
> > 2021-04-23 05:55:23.593 CEST [2317] FEHLER: Speicher aufgebraucht
>
Am Fri, Apr 23, 2021 at 10:48:24AM +0200 schrieb Laurenz Albe:
> > The serverlog has around this time (sorry for German):
> >
> > 2021-04-23 05:55:23.591 CEST [2317] LOG: unvollständige Message vom Client
> > 2021-04-23 05:55:23.593 CEST [2317] FEHLER: Speicher aufgebraucht
> > 2021-04-23 05:55:
On Fri, 2021-04-23 at 10:15 +0200, Matthias Apitz wrote:
> We face (somehow reproducible) the following situation with a 13.1
> server and a client written in ESQL/C:
>
> # ps ax | grep post
> ...
> 27106 ?Ss 0:00 postgres: sisis sisis ::1(49518) idle in
> transaction
>
> # lsof | gr
Hello,
We face (somehow reproducible) the following situation with a 13.1
server and a client written in ESQL/C:
# ps ax | grep post
...
27106 ?Ss 0:00 postgres: sisis sisis ::1(49518) idle in transaction
# lsof | grep 49518
INDEX 27074 sisis2u IPv6
14 matches
Mail list logo
