| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Greg Kemnitz <gjkemnitz(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tablespace storage bug... |
| Date: | 2024-12-05 01:09:29 |
| Message-ID: | CAKFQuwan5BGV+irGebgKYCiTTdmX_xq-p6rAyXdw_fJaezP9Uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, December 4, 2024, Greg Kemnitz <gjkemnitz(at)gmail(dot)com> wrote:
> In PG version 16.6.1.pgdg24.04+1 on Ubuntu:
>
> CREATE TABLE xxx (a int, b int, PRIMARY KEY (a)) TABLESPACE xyz;
>
> will store the table's base storage in xyz, but will store the table's
> PRIMARY KEY storage in pg_default.
>
> This seems a weird behavior and caused a load of a six billion row table
> to crash as the / partition unexpectedly ran out of space.
>
> Workaround:
>
Read the docs for the “using index tablespace” clause.
https://www.postgresql.org/docs/current/sql-createtable.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2024-12-05 01:46:33 | Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function |
| Previous Message | Greg Kemnitz | 2024-12-05 01:04:16 | Tablespace storage bug... |