| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: COPY write load on primary impacting replica? |
| Date: | 2022-01-20 07:57:30 |
| Message-ID: | e242f5a7e478c48a506960744f870f6de8a1e39d.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2022-01-19 at 17:27 -0800, Wells Oliver 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.
That is a feasible idea.
Make sure to set "max_standby_streaming_delay" high enough that COPY
won't get canceled.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daulat | 2022-01-20 09:56:54 | Password authorization |
| Previous Message | Licio Matos | 2022-01-20 02:01:02 | Re: COPY write load on primary impacting replica? |