Hi Avi,
Based on the slot name this is an initial sync worker being created by the
Logical Replication supervisor. Subscriber started an initial sync either
failed to create the slot and now thinks it exists and keeps trying to drop
it on the publisher or another process dropped the slot on the p
how about this:
jit = off ?
Marcin
On Wed, 17 Apr 2024 at 19:33, Johnathan Tiamoh
wrote:
> 1) How did you upgrade? pg_dump or pg_upgrade?
>
> I use pg_ugrade with kink option.
>
> 2) Did you run ANALYZE to collect statistics after the upgrade?
>
>
> Yes. I ran vacuumdb-analyze in stages after
1) How did you upgrade? pg_dump or pg_upgrade?
I use pg_ugrade with kink option.
2) Did you run ANALYZE to collect statistics after the upgrade?
Yes. I ran vacuumdb-analyze in stages after the upgrade
3) Did you transfer the configuration, or did you just create a new
cluster with the default
> On Apr 17, 2024, at 10:13, Johnathan Tiamoh wrote:
> I performed an upgrade from postgresql-9.5 to postgresql-14 and the
> performance has degraded drastically.
>
> Please, is they any advice on getting performance back ?
Run:
VACUUM (ANALYZE, VERBOSE);
More seriously (although
On 4/17/24 19:13, Johnathan Tiamoh wrote:
> Hello,
>
>
> I performed an upgrade from postgresql-9.5 to postgresql-14 and the
> performance has degraded drastically.
>
> Please, is they any advice on getting performance back ?
>
There's very little practical advice we can provide based on this
Hello,
I performed an upgrade from postgresql-9.5 to postgresql-14 and the
performance has degraded drastically.
Please, is they any advice on getting performance back ?
King Regards
Johnathan T.
On 2024-04-17 23:06, jack wrote:
As a result of this I will be checking the RAM on all my machines once
a month or the moment a machine starts to act strange.
Once a month is overkill, and unlikely to be useful. :)
With server or enterprise grade hardware, it'll support "ECC" memory.
That ha
Thanks Laurenz and David
Regards,
Sasmit Utkarsh
+91-7674022625
On Tue, 16 Apr, 2024, 16:58 Laurenz Albe, wrote:
> On Tue, 2024-04-16 at 16:30 +0530, Sasmit Utkarsh wrote:
> > msshctd=> SELECT setval(pg_get_serial_sequence('mqa_flfo_cstr', 'id'),
> coalesce(MAX(id), 1)) from mqa_flfo_cstr;
> >
Fixed a typo...
Hi Experts,
For a second time in the past few months I'm getting the following errors in
Postgres log. Last time it was solved when I reset all Postgres pods. Now
reset no longer helps. Logical replication is not working even after I
performed the reset.
Any ideas what is wr
Hi Experts,
For a second time in the past few months I'm getting the following errors in
Postgres log. Last time it was solved when I reset all Postgres pods. Now
reset no longer helps. Logical replication is now working even after I
performed the reset.
Any ideas what is wrong?
ERROR: re
That kind of support for “damaged ram” you have it with ECC memory on CPU’s
that support it.
XEON cpus for example.
> On 17 Apr 2024, at 15:06, jack wrote:
>
> uld advise me if there was ever an issue with me
I discovered that one of the memory sticks in the machine was damaged.
Running memtest86 on the machine generated many RAM errors.
This was causing the strange bi-polar errors in postgresql.
The hardware technician explained that he sees this often and that there is no
one cause for such problems
> De: "yudhi"
> À: "gparc"
> Cc: "Juan Rodrigo Alejandro Burgos Mella" ,
> "pgsql-general"
> Envoyé: Mercredi 17 Avril 2024 09:42:49
> Objet: Re: Controlling resource utilization
> On Wed, 17 Apr, 2024, 12:40 pm , < [ mailto:gp...@free.fr | gp...@free.fr ] >
> wrote:
>>> De: "Juan Rodrigo Alej
On Wed, 17 Apr, 2024, 12:40 pm , wrote:
>
>
> --
>
> *De: *"Juan Rodrigo Alejandro Burgos Mella"
> *À: *"yudhi s"
> *Cc: *"pgsql-general"
> *Envoyé: *Mardi 16 Avril 2024 22:29:35
> *Objet: *Re: Controlling resource utilization
>
> ALTER ROLE SET statement_timeout =
> De: "Juan Rodrigo Alejandro Burgos Mella"
> À: "yudhi s"
> Cc: "pgsql-general"
> Envoyé: Mardi 16 Avril 2024 22:29:35
> Objet: Re: Controlling resource utilization
> In postgreSQL, that can be done at a session level, or at a general level (in
> the postgresql.conf configuration file)
> Atte
15 matches
Mail list logo
