| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Partitioned tables and [un]loggedness |
| Date: | 2024-09-03 07:59:18 |
| Message-ID: | Zta_CFeFCx7bMBL8@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 02, 2024 at 08:35:15PM -0500, Nathan Bossart wrote:
> On Tue, Sep 03, 2024 at 09:22:58AM +0900, Michael Paquier wrote:
>> Okay. This is going to be disruptive if we do nothing about pg_dump,
>> unfortunately. How about tweaking dumpTableSchema() so as we'd never
>> issue UNLOGGED for a partitioned table? We could filter that out as
>> there is tbinfo->relkind.
>
> That's roughly what I had in mind.
An idea is attached. The pgbench bit was unexpected.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| unlogged-part-v3.patch | text/x-diff | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2024-09-03 08:39:08 | Re: DOCS - pg_replication_slot . Fix the 'inactive_since' description |
| Previous Message | Peter Smith | 2024-09-03 07:52:53 | Re: DOCS - pg_replication_slot . Fix the 'inactive_since' description |