Magnus,
PostgreSQL 14.6 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6)
10.2.1 20210110, 64-bit
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
It is docker container if it matters and yep, possibly slow and unreliable
network also is an issue.
So you're assuming the
On Tuesday, March 26, 2024, Siraj G wrote:
>
>
> I am from Oracle background. In Oracle, we grant select_catalog_role or
> select any dictionary role to users who want to study performance data. I
> am trying to get similar information on the roles or privileges in PgSQL
> that we might want to
> On Mar 26, 2024, at 22:30, Siraj G wrote:
> I am from Oracle background. In Oracle, we grant select_catalog_role or
> select any dictionary role to users who want to study performance data. I am
> trying to get similar information on the roles or privileges in PgSQL that we
> might want
Greetings!
I am from Oracle background. In Oracle, we grant select_catalog_role or
select any dictionary role to users who want to study performance data. I
am trying to get similar information on the roles or privileges in PgSQL
that we might want to request to investigate the performance
I use a script to restore a backup to create a testing copy of the
database. I set the following in postgresql.auto.conf:
recovery_target = 'immediate'
recovery_target_action = 'promote'
In the logs I get "recovery stopping after reaching consistency" then a
moment later "database system is
On Tue, Mar 26, 2024 at 3:19 PM Ц wrote:
> Greetings!
> I’ve faced with strange behavior when I see a lot of active sessions
> started hours ago while statement_timeout = '30min'.
> All of them are fetching from cursors.
>
> Typical session looks like:
> backend_start| 2024-03-26
Don Seiler writes:
> On Tue, Mar 26, 2024 at 9:09 AM Tom Lane wrote:
>> ... So you could overshoot the specified target by
>> more or less the amount of WAL that could be emitted between two
>> checkpoints. Perhaps it's tighter nowadays, but I really doubt that
>> it's
Greetings!
I’ve faced with strange behavior when I see a lot of active sessions started
hours ago while statement_timeout = '30min'.
All of them are fetching from cursors.
Typical session looks like:
backend_start | 2024-03-26 14:34:20.552594+03
xact_start | 2024-03-26
On Tue, Mar 26, 2024 at 9:09 AM Tom Lane wrote:
> My immediate reaction is that 3% is a mighty small margin for error.
> I don't know exactly how max_slot_wal_keep_size is enforced these
> days, but in the past restrictions like that were implemented by
> deciding during a checkpoint whether to
Don Seiler writes:
> With our recent upgrade to PG 15, we've put the max_slot_wal_keep_size into
> place, setting it about 3% lower than the size of the volume dedicated to
> pg_wal. However last night we had an incident where the volume filled up
> while we were performing a massive insert from
Good morning,
With our recent upgrade to PG 15, we've put the max_slot_wal_keep_size into
place, setting it about 3% lower than the size of the volume dedicated to
pg_wal. However last night we had an incident where the volume filled up
while we were performing a massive insert from one table
Hello, it looks like I've run into the same issue as you. I exhausted the disk
space while executing DDL operations, and then after crash recovery, I found
there were orphaned files.
I believe the reason is that due to the lack of space, some of the WAL logs were
not persisted, such as the
12 matches
Mail list logo
