| From: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Michael Banck <mbanck(at)gmx(dot)net>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Frits Hoogland <frits(dot)hoogland(at)gmail(dot)com> |
| Subject: | Re: The ability of postgres to determine loss of files of the main fork |
| Date: | 2025-10-07 10:57:43 |
| Message-ID: | CAKZiRmz8FzrPg_r1uRYN4J04zv2CTdk=KoCpxCXf5P-M7pQvDw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 6, 2025 at 2:07 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Mon, 2025-10-06 at 11:19 +0200, Jakub Wartak wrote:
> > Anyway, I do not know if opening all the files on startup (or just
> > crash-recovery?) is the proper way
>
> I am not sure if you understand the problem at hand: how can you
> tell that a segment of a relation is missing? You have to know that
> there should be a file before you can try to open it.
I'm pretty aware that PG doesnt track the relation segment count, but
possibly it should as without that nasty stuff can happen. Then the
discussion was mostly on how practical it would be to just open all
files on big DBs during startup (if we know them in advance), but it
is just one of the ideas I suspect, I've just checked those timings
out of curiosity.
Anyway there's also a referenced earlier idea for single file relation
model by Thomas.
Another fun-fact: see READ_ONLY_OPEN_DELAYED details in Oracle.
-J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-10-07 11:19:26 | Re: Improve pg_sync_replication_slots() to wait for primary to advance |
| Previous Message | Richard Guo | 2025-10-07 10:56:48 | Re: Eager aggregation, take 3 |