| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | veem v <veema0000(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: How to do faster DML |
| Date: | 2024-02-12 10:30:09 |
| Message-ID: | CAFCRh-8MwD-jj1-EPB4QfD1BBQKv3RcCu16WHkzFk6--BOsp3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 12, 2024 at 7:50 AM veem v <veema0000(at)gmail(dot)com> wrote:
> I think that's not much of a concern with PostgreSQL because you can't
>> update a row in-place anyway because of MVCC.
>
>
> Good to know. So it means here in postgres, there is no such concern like
> "row chaining", "row migration" etc.
>
which we normally have in a non mvcc database (like Oracle say).
>
Don't confuse MVCC (Multi-Version Concurrency Control), and various
DB-specific MVCC implementation details.
BOTH Oracle and PostgreSQL *are* MVCC (read Tom Kyte). But they happen to
use very different implementations.
SQLite in WAL mode is also MVCC, but using yet another implementation.
All (MVCC) DBs do it differently, but achieve the same effect; albeit with
different trade-offs. --DD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johnathan Tiamoh | 2024-02-12 13:31:02 | Re: Safest pgupgrade jump distance |
| Previous Message | Justin Clift | 2024-02-12 10:15:31 | Re: Safest pgupgrade jump distance |