| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | sanyam jain <sanyamjain22(at)live(dot)in> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Burst in WAL size when UUID is used as PK while full_page_writes are enabled |
| Date: | 2017-10-27 11:54:09 |
| Message-ID: | CAA4eK1+nYnBwy6+R0fp9yNd_0T2ACoso0gE2Sgcvp84C-Wk2Vg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 27, 2017 at 11:26 AM, sanyam jain <sanyamjain22(at)live(dot)in> wrote:
> Hi,
>
> I was reading the blog
> https://blog.2ndquadrant.com/on-the-impact-of-full-page-writes .
>
> My queries:
>
> How randomness of UUID will likely to create new leaf page in btree index?
> In my understanding as the size of UUID is 128 bits i.e. twice of BIGSERIAL
> , more number of pages will be required to store the same number of rows and
> hence there can be increase in WAL size due to FPW .
> When compared the index size in local setup UUID index is ~2x greater in
> size.
>
You might want to give a try with the hash index if you are planning
to use PG10 and your queries involve equality operations.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-10-27 12:06:53 | Re: Burst in WAL size when UUID is used as PK while full_page_writes are enabled |
| Previous Message | Peter Eisentraut | 2017-10-27 11:31:09 | Re: [GENERAL] Postgres 10 manual breaks links with anchors |