MIME-Version: 1.0
From: Wells Oliver <wells.oliver@gmail.com>
Date: Sat, 16 Nov 2024 16:33:10 -0800
Message-ID: 
 <CAOC+FBVyTiuOMF92pQG3QOrE9j8qFegvZLoi-3UmdhFNg94e2A@mail.gmail.com>
Subject: RDS restore failed due to WAL log and disk space-- any tidy fixes?
To: pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000017a10062710f446"
Archived-At: 
 <https://www.postgresql.org/message-id/CAOC%2BFBVyTiuOMF92pQG3QOrE9j8qFegvZLoi-3UmdhFNg94e2A%40mail.gmail.com>
Precedence: bulk

--000000000000017a10062710f446
Content-Type: text/plain; charset="UTF-8"

I provisioned an RDS instance with 2500GB space and began the restore of a
database I know to be about 1750 GB using 16 jobs.

Unfortunately, it died very near the end when it ran out of disk space due
to WAL log usage. Lots of:

2024-11-17 00:07:09 UTC::@:[19861]:PANIC:  could not write to file
"pg_wal/xlogtemp.19861": No space left on device


And then kaboom.

I'm wondering what my course of action should be. Can I disable/reduce WAL
during a restore? wal_level is set to replica, can this temporarily be set
to minimal? Should I just eat the extra costs to add headroom for the WAL?
Would using fewer jobs during a restore reduce the amount of WAL created?

I appreciate it.


-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

--000000000000017a10062710f446
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div class=3D"gmail_default" style=3D"font-size:small=
">I provisioned an RDS instance with 2500GB space and began the restore of =
a database I know to be about 1750 GB using 16 jobs.</div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">Unfortunately, it died very near the end when i=
t ran out of disk space due to WAL log usage. Lots of:</div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><table role=3D"table" style=3D"font-size:12px=
;font-family:Monaco,Menlo,Consolas,&quot;Courier Prime&quot;,Courier,&quot;=
Courier New&quot;,monospace"><tbody><tr><td style=3D"max-width:1520.1px"><d=
iv><pre style=3D"font-family:monospace,monospace;font-size:1em;margin-top:0=
px;margin-bottom:0px">2024-11-17 00:07:09 UTC::@:[19861]:PANIC:  could not =
write to file &quot;pg_wal/xlogtemp.19861&quot;: No space left on device</p=
re></div></td></tr><tr></tr></tbody></table><br class=3D"gmail-Apple-interc=
hange-newline"></div><div class=3D"gmail_default" style=3D"font-size:small"=
>And then kaboom.</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">I&#39;m=
 wondering what my course of action should be. Can I disable/reduce WAL dur=
ing a restore? wal_level is set to replica, can this temporarily be set to =
minimal? Should I just eat the extra costs to add headroom for the WAL? Wou=
ld using fewer jobs during a restore reduce the amount of WAL created?</div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">I appreciate it.</div><br cle=
ar=3D"all"></div><div><br></div><span class=3D"gmail_signature_prefix">-- <=
/span><br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmai=
l_signature"><div dir=3D"ltr"><div>Wells Oliver<br><a href=3D"mailto:wellso=
liver@gmail.com" target=3D"_blank">wells.oliver@gmail.com</a></div></div></=
div></div>

--000000000000017a10062710f446--