Hi all,
I have a case on pg12.9 - rhel8 which crashed a long time ago and now in
log keep saying:
automatic vacuum of table "dbnamexx.pg_catalog.pg_statistic"automatic
vacuum of table "dbnamexx.pg_catalog.pg_class"automatic vacuum of table
"dbnamexx.pg_toast.pg_toast_2619"
automatic vacuum of ta
Thanks for the quick reply! NP, I was just being extra cautious after upgrade.
From: Tom Lane
Sent: Wednesday, May 15, 2024 6:50 PM
To: Dmitry O Litvintsev
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Seeing new stuff in log after upgrading from 11
Dmitry O Litvintsev writes:
> After upgrade 11 -> 15 started to see these messages in hot standby log:
> < 2024-05-15 17:20:24.164 CDT 151879 > LOG: restartpoint complete: wrote
> 296338 buffers (28.3%); 0 WAL file(s) added, 134 removed, 0 recycled;
> write=1619.469 s, sync=0.022 s, total=161
Hi,
After upgrade 11 -> 15 started to see these messages in hot standby log:
< 2024-05-15 17:20:24.164 CDT 151879 > LOG: restartpoint complete: wrote
296338 buffers (28.3%); 0 WAL file(s) added, 134 removed, 0 recycled;
write=1619.469 s, sync=0.022 s, total=1619.539 s; sync files=1492,
long
On 5/15/24 01:08, HORDER Philip wrote:
Classified as: {OPEN}
Backups of this db are created with:
pg_dump --file=fsm.dmp -Fc --blobs --oids --dbname=lfm --host=localhost
--port= --username=superuser
From your original post:
"Running Postgres 15.3 ..."
--oids have not been supported wi
Hi
parallel worker are used for parallel execution of the queries and you can
find the help in the below link.
https://www.postgresql.org/docs/current/how-parallel-query-works.html
Its controlled by following parameters.
max_worker_processes = 6
max_parallel_workers_per_gather = 3
max_parallel_
On Wed, 2024-05-15 at 15:17 +0300, Danut Soare wrote:
> The difference was less than 32 except one sequence with difference equal to
> 32
>
> The cache used for sequence creation was 1.
Great. Then everything is working as expected.
Yours,
Laurenz Albe
So what is this particular "background worker" I'm seeing, given that I
have no replication or extensions?
Searching the logs I found entries like the following:
LOG: background worker "parallel worker" (PID 93384) exited with exit code 1
This got logged when I killed a simple SELECT query tha
On Wed, 15 May 2024 at 21:08, Sašo Gantar wrote:
> this query takes more than 8 seconds,
> if i remove "AND ((pgn.nspname='servicedesk'))" and test it, it takes <1s
Including the EXPLAIN rather than EXPLAIN (ANALYZE, BUFFERS) isn't
very useful as there's no way to tell if the planner's estimates
On Wed, 2024-05-15 at 11:03 +0300, Danut Soare wrote:
> I’m upgrading the PostgreSQL version from 12 to 16 using pg_upgrade utility
> with -k option. After upgrading the database, before starting any application
> processing, on checking the last value of some sequences, the value has been
> chang
this query takes more than 8 seconds,
if i remove "AND ((pgn.nspname='servicedesk'))" and test it, it takes <1s
SELECT COALESCE(Json_agg(Row_to_json(info)), '[]' :: JSON) AS TABLES
FROM
(WITH partitions AS
(SELECT array
(WITH partitioned_tables AS
(SELECT array
Hi everyone.
I’m upgrading the PostgreSQL version from 12 to 16 using pg_upgrade utility
with -k option. After upgrading the database, before starting any application
processing, on checking the last value of some sequences, the value has been
changed to a value different from the original valu
Classified as: {OPEN}
Backups of this db are created with:
pg_dump --file=fsm.dmp -Fc --blobs --oids --dbname=lfm --host=localhost
--port= --username=superuser
Restore is run with:
dropdb --port= --maintenance-db=postgres --username=superuser --if-exists
lfm
pg_restore -Fc --create -
13 matches
Mail list logo
