Re: pgbench with partitioned tables - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: pgbench with partitioned tables
Date
Msg-id CAAKRu_YmBx8ssfrs-vTYTdcWdQCtWYpn7oke4xEx-+6oNBqtbw@mail.gmail.com
Whole thread Raw
In response to Re: pgbench with partitioned tables  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Tue, Feb 11, 2025 at 2:29 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> I was testing with this with the intent to commit it and noticed that
> it does change behavior in one way -- previously if you created an
> unlogged table with the same schema as one of the pgbench tables and
> then used client-side data generation, it would COPY FREEZE data into
> that table. With the patch, it would no longer do that. I can live
> with that, but I thought it was worth mentioning.

whoops, ignore this! I got turned around in the
RELKIND_/RELPERSISTANCE_ macro section of pg_class.h.

Anyway, I've committed this patch. I updated the docs but didn't add a
test this time. I'm still not sure how much we want to codify our
support of pgbench loading data into different kinds of user-defined
tables.

- Melanie



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: AIO v2.3
Next
From: Jeff Davis
Date:
Subject: Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators