| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | jack <jack4pg(at)a7q(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: constant crashing |
| Date: | 2024-04-15 02:08:56 |
| Message-ID: | CAKFQuwbjojQtSv=SeFnvx6XXrJQ2k7rsNR=rCOAfM0f+E=BmHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Apr 14, 2024 at 6:58 PM jack <jack4pg(at)a7q(dot)com> wrote:
> But the current i9 machine is a machine from only 4 years ago which should
> have no issues.
>
>
That is a non sequitur. Besides, if the current code is a representative
example you've probably given it the effective usage of 8 years.
Whether related or not to this error you really should be doing all those
updates on a temporary or unlogged staging table and getting WAL generation
out of the equation.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Seinlet | 2024-04-15 06:52:48 | Failing streaming replication on PostgreSQL 14 |
| Previous Message | David Rowley | 2024-04-15 01:59:00 | Re: constant crashing |