| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Jim Mlodgenski <jimmy76(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Large files for relations |
| Date: | 2023-05-24 00:34:27 |
| Message-ID: | CA+hUKGJtzXsX-ELx6M-hM83ZY3iqXpUf7HEbf=oFNGEP78MG7g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks all for the feedback. It was a nice idea and it *almost*
works, but it seems like we just can't drop segmented mode. And the
automatic transition schemes I showed don't make much sense without
that goal.
What I'm hearing is that something simple like this might be more acceptable:
* initdb --rel-segsize (cf --wal-segsize), default unchanged
* pg_upgrade would convert if source and target don't match
I would probably also leave out those Windows file API changes, too.
--rel-segsize would simply refuse larger sizes until someone does the
work on that platform, to keep the initial proposal small.
I would probably leave the experimental copy_on_write() ideas out too,
for separate discussion in a separate proposal.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-05-24 00:51:52 | Re: Handle SIGTERM in fe_utils/cancel.c |
| Previous Message | Michael Paquier | 2023-05-24 00:31:34 | Re: Make pgbench exit on SIGINT more reliably |