On Fri, Aug 9, 2024 at 1:02 AM David Rowley wrote:
> On Fri, 9 Aug 2024 at 02:12, Christophe Pettus wrote:
> > VACUUM FULL takes an exclusive lock on the table that it is operating
> on. It's possible that a connection becomes blocked on that exclusive lock
> waiting for the VACUUM FULL to fini
> On Aug 8, 2024, at 21:15, Ron Johnson wrote:
>
> "I see a lock, so let's cause another one!" That's crazy.
It's more "Oh, look, I need a connection to service this web request, but my
pool is empty, so I'll just fire up a new connection to the server," lather,
rinse, repeat. Pretty comm
On Thu, Aug 8, 2024 at 10:12 AM Christophe Pettus wrote:
>
>
> > On Aug 7, 2024, at 10:34, Costa Alexoglou wrote:
> >
> > Hey folks,
> >
> > I noticed something weird, and not sure if this is the expected
> behaviour or not in PostgreSQL.
> >
> > So I am running Benchbase (a benchmark framework)
On Fri, 9 Aug 2024 at 02:12, Christophe Pettus wrote:
> VACUUM FULL takes an exclusive lock on the table that it is operating on.
> It's possible that a connection becomes blocked on that exclusive lock
> waiting for the VACUUM FULL to finish, the application sees the connection
> stopped and
> On Aug 7, 2024, at 10:34, Costa Alexoglou wrote:
>
> Hey folks,
>
> I noticed something weird, and not sure if this is the expected behaviour or
> not in PostgreSQL.
>
> So I am running Benchbase (a benchmark framework) with 50 terminals (50
> concurrent connections).
> There are 2-3 add
On Thu, 8 Aug 2024 at 11:18, Costa Alexoglou wrote:
...
> So I am running Benchbase (a benchmark framework) with 50 terminals (50
> concurrent connections).
> There are 2-3 additional connections, one for a postgres-exporter container
> for example.
...
> So far so good, and with a `max_connecti
On Thu, Aug 8, 2024 at 5:18 AM Costa Alexoglou wrote:
> Hey folks,
>
> I noticed something weird, and not sure if this is the expected behaviour
> or not in PostgreSQL.
>
> So I am running Benchbase (a benchmark framework) with 50 terminals (50
> concurrent connections).
> There are 2-3 additiona
Hey folks,
I noticed something weird, and not sure if this is the expected behaviour
or not in PostgreSQL.
So I am running Benchbase (a benchmark framework) with 50 terminals (50
concurrent connections).
There are 2-3 additional connections, one for a postgres-exporter container
for example.
So
