Hello community,
I am checking my pg_stat_activity view,but something confused me.
Just like this:
postgres=# SELECT wait_event_type, wait_event FROM pg_stat_activity;
wait_event_type | wait_event
-+-
Activity| AutoVacuumMain
Activity| Logic
2022年9月8日(木) 17:37 BeginnerC :
>
> Hello community,
> I am checking my pg_stat_activity view,but something confused me.
> Just like this:
>
> postgres=# SELECT wait_event_type, wait_event FROM pg_stat_activity;
> wait_event_type | wait_event
> -+-
> Activit
We do have JIT enabled `jit=on` with `jit_above_cost=10`.
I am sorry but I don't quite understand what role JIT plays in
this situation with `auto_explain`. Could you please elaborate on that?
On Tue, 6 Sept 2022 at 00:29, Maxim Boguk wrote:
>
>
> On Tue, Aug 30, 2022 at 1:38 PM Matheus Mar
On Thu, Sep 08, 2022 at 04:37:00PM +0800, BeginnerC wrote:
> Hello community,
> I am checking my pg_stat_activity view,but something confused me.
> Just like this:
>
> postgres=# SELECT wait_event_type, wait_event FROM pg_stat_activity;
> wait_event_type | wait_event
> -+--
This is an issue when PostgreSQL is running inside a container. In my quest to
find an answer, I’ve discovered three instances that it has come up and various
people have talked about fixes but no one seemed to notice what I found.
I opened an issue here[1].
From within the container, files wh
Perry Smith writes:
> From within the container, files which I assume are created by
> PostgreSQL are ending up being owned by root rather than Postgres.
If it looks that way from *inside* the container, that's not good
--- wouldn't that prevent Postgres from reading the files?
> The reason I’m
On 9/8/22 23:05, Perry Smith wrote:
This is an issue when PostgreSQL is running inside a container. In my
quest to find an answer, I’ve discovered three instances that it has
come up and various people have talked about fixes but no one seemed
to notice what I found.
I opened an issue here[1
> On Sep 8, 2022, at 10:43 PM, Tom Lane wrote:
>
> Perry Smith writes:
>> From within the container, files which I assume are created by
>> PostgreSQL are ending up being owned by root rather than Postgres.
>
> If it looks that way from *inside* the container, that's not good
> --- wouldn't
On 9/9/22 00:08, Perry Smith wrote:
The data directory is outside so it is persistent. The pg_stat_tmp is inside
the data directory.
Ah, that's the reason. Docker daemon runs as root so if you do binding
mount, files will be owned by root. You may want to use normal Docker
volume and not an
