| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
| Cc: | Stephan Doliov <stephan(dot)doliov(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Hannu Krosing <hannuk(at)google(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Let's make PostgreSQL multi-threaded |
| Date: | 2023-06-09 22:29:24 |
| Message-ID: | ZIOnxKN6L1cRPPO2@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Dave Cramer (davecramer(at)postgres(dot)rocks) wrote:
> One thing I can think of is upgrading. AFAIK dump and restore is the only
> way to change the on disk format.
> Presuming that eventually we will be forced to change the on disk format it
> would be nice to be able to do so in a manner which does not force long
> down times
There is an ongoing effort moving in this direction. The $subject isn't
great, but this patch set (which we are currently working on
updating...): https://commitfest.postgresql.org/43/3986/ attempts
changing a lot of currently compile-time block-size pieces to be
run-time which would open up the possibility to have a different page
format for, eg, different tablespaces. Possibly even different block
sizes. We'd certainly welcome discussion from others who are
interested.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-06-09 23:22:57 | add non-option reordering to in-tree getopt_long |
| Previous Message | Jeff Davis | 2023-06-09 22:16:11 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |