| From: | Licio Matos <licio(dot)matos(at)gmail(dot)com> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: COPY write load on primary impacting replica? |
| Date: | 2022-01-20 02:01:02 |
| Message-ID: | CAK6Tc4P0rhq+bcVVa_USwC9AUQM39HGiaQuO55QWP5jJMSbNbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Why not make the COPY in small batch and intervals of seconds between them?!
Like COPY 10000 and wait 60 seconds for another batch.
On Wed, 19 Jan 2022 at 22:28 Wells Oliver <wells(dot)oliver(at)gmail(dot)com> wrote:
> Hi: I have an issue where a big big big COPY is thrashing a disk on a DB,
> my idea was to fire up a read replica of this DB and point my users to it
> for SELECT (read) operations, thereby hopefully (?) avoiding the disk usage
> caused by COPY on the primary.
>
> Wondering if this is foolish, whether the WAL log stuff would cause equal
> disk usage on the replica.
>
> Thanks!
>
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
>
--
Licio Matos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-01-20 07:57:30 | Re: COPY write load on primary impacting replica? |
| Previous Message | Wells Oliver | 2022-01-20 01:27:48 | COPY write load on primary impacting replica? |