| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Subject: | Re: Patch: dumping tables data in multiple chunks in pg_dump |
| Date: | 2026-01-28 21:33:48 |
| Message-ID: | CAMT0RQQuMNkgJBQhWwWKFX5oqPPCXYFYf=_iTKAFgWJHNOrJig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 28, 2026 at 10:27 PM Hannu Krosing <hannuk(at)google(dot)com> wrote:
>
> Hi David
>
> About documentation :
>
> On Fri, Jan 23, 2026 at 3:15 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> >
> > Aside from that, nothing in the documentation mentions that this is
> > for "heap" tables only.
On re-reading I finally understood what you meant - that the
chunking applies to only standard postgreSQL TAM called "heap"
Will add that as well. Would something like work
"This flag applies only to tables that use the standard PostgreSQL
Table Access Method (TAM) called "heap".
The tables that are using any custom TAM are dumped as if
--max-table-segment-pages was not set."
---
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-01-28 21:48:45 | Re: Race conditions in logical decoding |
| Previous Message | Hannu Krosing | 2026-01-28 21:27:30 | Re: Patch: dumping tables data in multiple chunks in pg_dump |