Re: In-placre persistance change of a relation

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: smithpb2250(at)gmail(dot)com
Cc: vignesh21(at)gmail(dot)com, nathandbossart(at)gmail(dot)com, jakub(dot)wartak(at)enterprisedb(dot)com, stark(dot)cfm(at)gmail(dot)com, hlinnaka(at)iki(dot)fi, barwick(at)gmail(dot)com, jchampion(at)timescale(dot)com, pryzby(at)telsasoft(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, rjuju123(at)gmail(dot)com, jakub(dot)wartak(at)tomtom(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: In-placre persistance change of a relation
Date: 2024-05-24 07:09:16
Message-ID: 20240524.160916.2199777355532445323.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rebased.

Along with rebasing, I changed the interface of XLogFsyncFile() to
return a boolean instead of an error message.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
v33-0001-Export-wal_sync_method-related-functions.patch text/x-patch 3.8 KB
v33-0002-Introduce-undo-log-implementation.patch text/x-patch 45.5 KB
v33-0003-In-place-table-persistence-change.patch text/x-patch 29.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2024-05-24 07:21:43 Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions
Previous Message Michael Paquier 2024-05-24 06:45:44 Re: Avoid possible dereference null pointer (src/backend/catalog/pg_depend.c)