public inbox for pgsql-general@postgresql.org  
help / color / mirror / Atom feed
Disconnecting from the server
3+ messages / 2 participants
[nested] [flat]

* Disconnecting from the server
@ 2026-05-17 02:29 Igor Korot <ikorot01@gmail.com>
  2026-05-17 02:50 ` Re: Disconnecting from the server David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Igor Korot @ 2026-05-17 02:29 UTC (permalink / raw)
  To: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>

Hi, ALL.
Let's say I'm debugging my application.

I establish a successful connection to the server and start
debugging.

During the debugging session I found a bug/issue.

In this case what I usually do is I stop and exit the debugger
essentially imitating the program crash.

What will happen in this case?

I presume the connection will be closed the socket becomes
available and the server will clear all resources associated with the
connection?

Or should I perform some clean-up on the server - some kind of "connection
pool reset" so that the resources associated with the connection will be
gone?

Please clarify.

Thank you.





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Disconnecting from the server
  2026-05-17 02:29 Disconnecting from the server Igor Korot <ikorot01@gmail.com>
@ 2026-05-17 02:50 ` David G. Johnston <david.g.johnston@gmail.com>
  2026-05-17 03:43   ` Re: Disconnecting from the server Igor Korot <ikorot01@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: David G. Johnston @ 2026-05-17 02:50 UTC (permalink / raw)
  To: Igor Korot <ikorot01@gmail.com>; +Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>

On Saturday, May 16, 2026, Igor Korot <ikorot01@gmail.com> wrote:
>
> Or should I perform some clean-up on the server - some kind of "connection
> pool reset" so that the resources associated with the connection will be
> gone?
>

There server doesn’t have a connection pool.

You can inspect what is connected to the server via the pg_stat_activity
view.

https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW

David J.


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Disconnecting from the server
  2026-05-17 02:29 Disconnecting from the server Igor Korot <ikorot01@gmail.com>
  2026-05-17 02:50 ` Re: Disconnecting from the server David G. Johnston <david.g.johnston@gmail.com>
@ 2026-05-17 03:43   ` Igor Korot <ikorot01@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Igor Korot @ 2026-05-17 03:43 UTC (permalink / raw)
  To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>

Hi, David,

On Sat, May 16, 2026 at 9:50 PM David G. Johnston
<david.g.johnston@gmail.com> wrote:
>
> On Saturday, May 16, 2026, Igor Korot <ikorot01@gmail.com> wrote:
>>
>> Or should I perform some clean-up on the server - some kind of "connection
>> pool reset" so that the resources associated with the connection will be
>> gone?
>
>
> There server doesn’t have a connection pool.

There is a reason I put quotes around that phrase. ;-)

>
> You can inspect what is connected to the server via the pg_stat_activity view.
>
> https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW

Thank you for the info.

I checked and there are no processes running.

Which means I don't need to clean up anything. ;-)


>
> David J.
>






^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2026-05-17 03:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-17 02:29 Disconnecting from the server Igor Korot <ikorot01@gmail.com>
2026-05-17 02:50 ` David G. Johnston <david.g.johnston@gmail.com>
2026-05-17 03:43   ` Igor Korot <ikorot01@gmail.com>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox