| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: MVCC and all that... |
| Date: | 2025-09-10 15:11:30 |
| Message-ID: | CANzqJaBMExaKVMnMWBDxR=iYcm=ofjpJp6KWkSXijhDU2g8NNg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Sep 10, 2025 at 11:08 AM Ellen Allhatatlan <
ellenallhatatlan(at)gmail(dot)com> wrote:
[snip]
> So, you have table X - it has 2M rows (say, 0.5 GB) in the first file
> (along with all the other tables). The 2GB limit is hit, more data is
> added. 0.7 GB is added to table X - these records go into a new
> database file - the table is split in two - you have 2 "extents" of
> 2GB with X split 0.5 - in extent1, 0.7 in extent2. All mixed up with
> other tables as well!
>
> That was the architectural flaw to which I was referring. Nothing to
> do with PG
>
You're gonna be in for a very rude surprise after adding 1GB of data to a
PG table...
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-09-10 15:15:35 | Re: MVCC and all that... |
| Previous Message | Ellen Allhatatlan | 2025-09-10 15:08:15 | Re: MVCC and all that... |