| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Sergey Tatarintsev <s(dot)tatarintsev(at)postgrespro(dot)ru> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench with partitioned tables |
| Date: | 2025-02-11 21:54:31 |
| Message-ID: | CAAKRu_YmBx8ssfrs-vTYTdcWdQCtWYpn7oke4xEx-+6oNBqtbw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 11, 2025 at 2:29 PM Melanie Plageman
<melanieplageman(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2025-02-11 22:04:45 | Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators |
| Previous Message | Andres Freund | 2025-02-11 21:43:22 | Re: AIO v2.3 |