| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Thomas Simpson <ts(at)talentstack(dot)to> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: filesystem full during vacuum - space recovery issues |
| Date: | 2024-07-18 20:32:49 |
| Message-ID: | CANzqJaCpSNZU8AaHPLS2Ms7WzsqBX0L1ZufD8cmUaLi78uA1=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Thu, Jul 18, 2024 at 3:01 PM Thomas Simpson <ts(at)talentstack(dot)to> wrote:
[snip]
> [BTW, v9.6 which I know is old but this server is stuck there]
>
> [snip]
> I know I'm stuck with the slow rebuild at this point. However, I doubt I
> am the only person in the world that needs to dump and reload a large
> database. My thought is this is a weak point for PostgreSQL so it makes
> sense to consider ways to improve the dump reload process, especially as
> it's the last-resort upgrade path recommended in the upgrade guide and the
> general fail-safe route to get out of trouble.
>
No database does fast single-threaded backups.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Simpson | 2024-07-18 20:53:23 | Re: filesystem full during vacuum - space recovery issues |
| Previous Message | Thomas Simpson | 2024-07-18 18:59:35 | Re: filesystem full during vacuum - space recovery issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2024-07-18 20:33:08 | Re: documentation structure |
| Previous Message | Nathan Bossart | 2024-07-18 20:29:19 | Re: improve performance of pg_dump with many sequences |