From: | Siddharth Jain <siddhsql(at)gmail(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Some questions about Postgres |
Date: | 2022-11-03 18:17:24 |
Message-ID: | CAPqV3pQTfpNj3_Onu+N2L5BvarnSUnW-c5N7YLK_0B1bH6TnUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Christophe. Yes that is the article and I read the response as well.
On Thu, Nov 3, 2022 at 10:42 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
> > On Nov 3, 2022, at 10:38, Siddharth Jain <siddhsql(at)gmail(dot)com> wrote:
> > I read an old article comparing MySQL to Postgres and wanted to get
> answers to following questions.
>
> Given your questions, I suspect that you read the technical note from Uber
> about why they switched back to MySQL from PostgreSQL. There are quite a
> few responses out there to it, including:
>
> https://thebuild.com/presentations/uber-perconalive-2017.pdf
>
> To answer the specific questions:
>
> 1. Yes, all PostgreSQL indexes point directly to tuples on disk. They do
> not point to a primary key (which a table might not even have).
>
> 2. Yes, each backend connection to PostgreSQL is a separate process. The
> usual way of mitigating any performance issues this might introduce is to
> use a pooler such as pgbouncer.
>
> 3. This is equivalent to PostgreSQL's shared buffers.
From | Date | Subject | |
---|---|---|---|
Next Message | Joanna Xu | 2022-11-03 20:55:36 | shutdown Postgres (standby) host causing timeout on other servers in replication |
Previous Message | Christophe Pettus | 2022-11-03 17:42:44 | Re: Some questions about Postgres |