| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
| Cc: | jack <jack4pg(at)a7q(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-14 18:11:23 |
| Message-ID: | CAKFQuwY5O6QK-bgbb+h34zhBdwL53ViuEH1OoHWmQXdZkHBL5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Apr 14, 2024 at 10:20 AM Francisco Olarte <folarte(at)peoplecall(dot)com>
wrote:
>
> If postgres does not supress redundant updates ( lots of people can
> answer that )
It does not. My other usual piece of advice along these lines, if doing
the transform outside the database is not desirable, is to at least ensure
you are doing them on a staging table that is defined as either being
temporary or unlogged. WAL production probably isn't causing the crash but
can definitely be an issue and is pointless to incur during most
transformation processing.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2024-04-14 19:18:13 | Re: constant crashing |
| Previous Message | Francisco Olarte | 2024-04-14 17:19:16 | Re: constant crashing |